The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Does each jira ticket has its unique email address, if it has how to find it?

Charlie Chen
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 4, 2022

Ideally, if Jira ticket has its unique email address, we no need to waste time copying email content to the comment section

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

5 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 4, 2022

Welcome to the Community!

No, it doesn't make any sense for a Jira issue to have an email address.  What use would it be?  Do you really want to have to build mail services that can handle 12 million individual email addresses for issues in an issue tracker?  (I picked 12 million because that's the largest Jira I've worked on in the last few years)

The create-or-comment email handlers work fine when it comes to incoming emails.  Set up one email address and a handler will read all the incoming emails there and parse them for existing issue data.  For a "create or comment" handler, the rule is "Look at the subject.  If I find an existing issue key in the subject, then convert the email to a comment.  If I do not, then create a new issue"