We have multiple projects on our JIRA 5.1 enstance and here's the scenario. There was an issue where a customer sent an email to Project A's email address, then it created a ticket in Project A. Our Support Staff responds to customer saying the question should be addressed by Project B. Customer forwards Support Staff's response to Project B's email address. The Ticket contains Project A's Id key and number. Customer's forward email was not received by Project B, even though customer's email that was sent to Project B's email address, the customer's email was actually sent back to Project A.
Is there a way to send an email to JIRA and JIRA will beable to parse out the project's email address and the ID key? Which then, it'll create a new ticket under another project, with a link showing what the original project was.
Community moderators have prevented the ability to post new answers.
JEMH has two features that operate in this area.
1. Subject IssueKey (comment) Regexps
This specifically addresses JIRA to JIRA email notifications in the scenario you give. The solution implemented is to provide a regular expression that matches the local systems prefix. For example, if in incoming email has a subject of:
[PStudio] (JEMH-1016) Non-jira notifications
and say 'PStudio' is your local JIRA prefix, then, any other remote JIRA that followed that structure but didn't have a matching name would _not_ be used to identify an issue for commenting, and so would be created.
2. Ignore Subject Issue Keys if...
A second feature is that if the addressee matches a project key, eg email@example.com, then that allocation takes precedence over the subject, meaning, that traffic with that subject will be restricted to only being able to create issues in that project, or comment on them (if the subject text resolves to an issue in that project).
3. Project Mapping
You can also map remote senders to specific projects, which achieves the 'parse email/create in new project bit, in conjuntion with the above. So, a from: address of your remote JIRA could be mapped to a particular target project, the subject would contain the remote issue key.
Given the email content may or may not contain a link to the remote JIRA, getting a 'link' to that remote JIRA isn't straight forward.
im sure JEMH could help, but it doesnt do exactly what you describe, its an 80/20 solution
Hello Community members! We have an upcoming research study for Confluence and we’d like to invite you to provide advice and answer questions. We’re developing a new experience for Inline Comment...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events