Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Tickets Automatically created on Reply / Reply-All

Hi All,

We are seeing this issue where after the ticket is created, replies and responses in the thread create new tickets in the system. 


This is what the thread looks like. All responding in the email chain:


It doesn't seem to happen every time. I've done a few tests to recreate, but was unable to. We see this quite frequently when my team or clients are responding to tickets. 

Curious if anyone has had this issue before or know how to prevent this from happening. 

2 answers

Hi @Supakij Ngamwongpaiboon ,

you may want to check out my brand new article "Quickfix ☝🤓 – Solve Duplicate Tickets from Emails with Customer Organizations" on exactly how to fix this issue. 😁

0 votes

Hello @Supakij Ngamwongpaiboon,

Thank you for reaching out to Atlassian Community!

When a customer replies to a notification and instead of adding a comment, a new ticket is created, it means that the person who replied to the notification doesn’t have permission on the ticket.

Only the reporter, request participants, and members of an organization the ticket was shared with can comment on a ticket.

Some common issues where new tickets are created:

  1. A ticket is created by CustomerA, and they receive a notification. CustomerA forwards the notification to CustomerB and CustomerB replies to the notification which will go to CustomerA but also to and it will create a new ticket because CustomerB wasn’t added to the ticket. 
  2. CustomerA creates a ticket add shares the ticket with an email that is group email/distribution list, so, many people will receive the notification and if they reply, a new ticket will be created, because who has permission on the ticket is the and not
  3. Another issue that happens frequently is that some people use a mail client like Outlook and they access more than one inbox on the mail client. So, they receive a notification on, but end up replying with which doesn’t have permission on the ticket.

With all this said, it’s important that the customer who created the ticket adds other customers as CC at the moment the ticket is created via email, so they will be added as a participant or after the ticket is created, in the customer portal there is an option called “+ Share” on the ticket where they can add the email address of the people they need to have access to the ticket. 

Hope this helps!

If you have any other questions regarding this matter, please let us know.

Kind regards,

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Asked in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

391 views 21 14
View question

Community Events

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

Events near you