How to make email work better email2issue
We are using bug tracking system, as most of the software development companies. Creating an issue is quite simple. Open bug tracking system, fill some inputs, upload attachments – done. Issue is created. Sometimes issue is described with multiple attachments (screenshots). Bug tracking system allows us to embed images into description. All issues come from users in a form of email.
It’s just slow, and time consuming. We have to read email, download attachments. Copy and paste body into proper field. Upload attachments and embed it again into proper place. It’s not rocket science but just takes a lot of time. Especially when you have multiple issues, with multiple attachments.
- AWS SES to handle incoming emails. Simple, fast, and reliable. Send email – get output as an object on S3 bucket – get notification via SNS with body of the email
- Go microservice to explode email to usable parts
"Html" : "",
"Markup" : ""
As simple as powerful it is, can be reused for any other purpose. Micro service get’s email body as an input, outputs JSON with structure and ready to use links to attachments.
- Just a simple post query to Issue Tracker API to create new issue.
Extras: email notification to issue reporter that given issue was created.