Our teams currently have separate projects in which they track issues belonging to their team. We’re currently using the email-to-Jira case; however, the following feature is impeding the support flow: If an email message contains an issue key in its subject line and that issue key exists in your JIRA installation, the handler will add the email message content as a comment on the issue, regardless of which project the issue is in.
Please can we request the option to only consider cases in the specific project linked to the mail handler? In that way, any messages sent to the project specific email address will only populate the linked project. Since our teams only look in their project, the current functionality would result in lost cases.
But what happens when a user really does need to comment on an issue in another project? And why are they including an issue key from another project when they're trying to create issues in your target project?
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs