Don't like JIRA's Mail Handler? Extend it with SES and Lambda.

tportela1 — Wed, 10 Apr 2019 18:36:19 +0000

In my current work environment, Jira administration is handled by a separate team. I had created service accounts to be utilized by the Jira mail handler but then realized the mail handler lacks a lot of functionality! What do you mean you can't set component, issueType, or assignee dynamically?

Hm. That would just not do.

I decided to leverage the JIRA API and Amazon's Simple Email Service, along with Lambda.

Let's break it down step by step. First is configuring Amazon's Simple Email Service to receive the email and then consequently write it to S3. Note: the only way (currently) to extract the body of an email utilizing SES is to either write it to Simple Notification Service (SNS) or Simple Storage Service (S3). I have another article that lines out how to create this if you need help.

In Lambda, below is my code. I utilized an amazing Atlassian Python library.

import json, requests, email, boto3, urllib, time, os, base64, re
from JiraPy import *

def handler(event, context):

    s3 = boto3.client('s3')
    s3r = boto3.resource('s3')
    outputBucket = "jira"

    bucket = event['Records'][0]['s3']['bucket']['name']
    key = urllib.unquote_plus(event['Records'][0]['s3']['object']['key']).decode('utf8')


    try:
        if not outputBucket:
            global outputBucket
            outputBucket = bucket

        # Use waiter to ensure the file is persisted
        waiter = s3.get_waiter('object_exists')
        waiter.wait(Bucket=bucket, Key=key)
        response = s3r.Bucket(bucket).Object(key)

        # Read the raw text file into a Email Object
        msg = email.message_from_string(response.get()["Body"].read())
        messageTo = msg['To']
        messageFrom = msg['From']
        messageSubject = msg['Subject']
        messageBody = ''
        if msg.is_multipart():
            for part in msg.walk():
                ctype = part.get_content_type()
                cdispo = str(part.get('Content-Disposition'))
                # skip any text/plain (txt) attachments
                if ctype == 'text/plain' and 'attachment' not in cdispo:
                    messageBody = part.get_payload(decode=True)  
                    break
    else:
            messageBody = msg.get_payload(decode=True)

        if len(msg.get_payload()) == 2:
            attachment = msg.get_payload()[1]

        else:
            data = messageSubject.split('|')
            projectKey = data[0]
            issueType = data[1]
            component = data[2]
            summary = data[3]
            print(projectKey, issueType, messageFrom, component, summary)
            createIssue(projectKey, issueType, messageFrom, component, summary, messageBody)

    except Exception as e:
        print(e)
        raise e

The Jira portion of the script looks like:

def createIssue(projectKey, issueType, assignee, component, summary, messageBody):
    if issueType == "Epic":
        jira.issue_create(fields={
        'project': {'key': projectKey},
        'issuetype': {
            "name": issueType},
        'customfield_10605': summary,
        'assignee': {'name': assignee},
        'components': [{'name': component}],
        'summary': summary,
        'description': messageBody,
        })
    else:
        jira.issue_create(fields={
        'project': {'key': projectKey},
        'issuetype': {
            "name": issueType},
        'assignee': {'name': assignee},
        'components': [{'name': component}],
        'summary': summary,
        'description': messageBody,
        })

def updateIssue(issueKey, messageBody):
    jira.issue_add_comment(issueKey, messageBody)

Pretty simple!

Here is a visual representation of what it looks like for the end user.

"Email flow for End User"

Curious to hear your thoughts, hopefully this will be useful to someone else in the same predicament.

Thinking Beyond the LAMP Stack

tportela1 — Mon, 14 Jan 2019 18:59:08 +0000

Well, hello there. I've had a couple people contact me and ask me to write a post about a project I had completed. This is that post.

I recently had a project come my way where I need to accept user input in the form of an excel sheet, parse through the rows and cells, and post the responses to a third party system, all while generating logs to the original submitter.

Hm.

Immediately my mind went to a traditional LAMP (Linux, Apache, MySQL, PHP) stack website where users log in, upload their sheet, and results appear there.

It seemed to intrusive through, to ask my users to go through these extra steps. Think of the documentation I'd have to write..

Instead, I thought differently. Most individuals in a work environment use email. How do I harness that?

With AWS' SES (Simple Email Service), S3, and Lambda.

I created a departmental mailbox to use for the purpose of receiving emails from users with an attachment, something simple like risk@company.org, with certain subjects or phrases triggering a mail rule to redirect the email to... aws-risk@email.prod.aws.edu (more on that in the next paragraph).

I utilized Amazon Web Services Route 53 to create a DNS MX record for this purpose-- I named this one email.prod.aws.edu Note: aws.edu is a registered domain in route 53 for the purposes of this scenario.

Using Simple Email Service I was able to configure aws-risk@email.prod.aws.edu to immediately, upon email arrival, save its contents to an S3 bucket.

Here's where those of you familiar with Lambda and AWS will "ahhh" to. One of the triggers for a Lambda function is exactly that-- an object created in S3!

"Small section of the lambda function that checks for the item written in S3"

I was able to write all the code in Python, to parse through the rows and cells in the sheet, POST contents to third party system, and send a log back to the user back through SES. All through that one Lambda function, that awesome S3 bucket, and of course, the hero of the show, SES.

DEV Community: tportela1

Don't like JIRA's Mail Handler? Extend it with SES and Lambda.

Thinking Beyond the LAMP Stack