The vast majority of our clients continue to interact with the support team through the email channel. By default, JIRA looks for the request ID in the subject and headers of the message. So, if a message contains in its subject something like “[SD-123456] Please help me”, JIRA will look for a request #SD-123456 and put the message body in this request.
Seems like this strategy has some flaws and doesn’t prevent from creating new requests on the same matter.
In my past experience, I had been using Wrike for managing teamwork. In Wrike, you receive messages from an email address of special format like email@example.com. So, if you reply to firstname.lastname@example.org, your message will be easily sorted to request #123456 preventing any mistakes.
In this article, I’m explaining how to make it work in the same manner in JIRA.
Formatting reply-address for email notifications of JIRA SD helps with the following:
1. Avoid sorting mistakes: placing a comment in a wrong request, opening duplicate reqeusts
2. Comments of non-customers will be correctly sorted, still preventing them from disclosing other comments in a request.
3. Service Desk agents can easily forward any message to this special address if they want just attach to it a bunch of files from a client. Great for those who interacts with SD from a smartphone.
- Self-hosted email server. We use Postfix.
- JIRA Server. Mine was 7.3.0
- Jira Email This Issue Add-on https://marketplace.atlassian.com/apps/4977/email-this-issue
Mail Server Configuration
Basically, you have to configure support for Address Tags in your mail server. I used this article as an instruction: https://www.stevejenkins.com/blog/2011/03/how-to-use-address-tagging-usertagexample-com-with-postfix/
Most of the documentation says that you just need to set Postfix’s
$recipient_delimitervariable to the (set of) character(s) you want to use as a delimiter, like
recipient_delimiter = +. That’s fine if you’re just using local delivery. But when you use Dovecot’s LDA (or other LDA), you should also modify how it’s called in
Setup Incoming Mail Server:
Create a Mail Handler in JIRA Email This Issue
Create a new Field Context in JIRA Email This Issue
Create a context to make JIRA send notifications from a specially formatted email address:
Since version 18.104.22.168 the add-on JIRA Email This Issue is able to use a reg-exp rules in the Email Address Exclusion Field. Why it is useful? When your customers send a message to your specially-formatted address “email@example.com”, JETI will create a new user with username “firstname.lastname@example.org”. While there is no harm in it, still I prefer to keep my user database clean of fake users.
- Send a message to email@example.com, where 123456 is ID of an existing issue. Your comment should be placed in the request.
- Send a message to firstname.lastname@example.org, where 123456 is ID non-existent. A new request should be created.
- Send a message to email@example.com from a customer who is not a participant of request #123456. A comment should be added to this request, but from a default user which was configured in JETI.