We run Jira Service management, and when a ticket is in Closed status, we have set up propriety to close the comment section - but there are customers that create tickets via email, and if we close a ticket, and they reply again by email - we want to create another ticket and link it back to the original one - closed.
Is this possible?
This is possible with the use of Automation. I have done something similar for my cloud instance, though we do not have the restriction for commenting on the closed issues.
Please refer to the below screenshot for details of the automation. This can be customised as per your use case.
Please share if any guidance on customisation is required.
Kindly accept the answer if this helps resolve the query.
To mimic your scenario, I have implemented the restriction on comments for closed tickets. Post this, reply to that mail thread for the closed ticket created a new ticket and informed about the new ticket as well.
The comment was captured as the description of the new ticket.
Please refer to the below screenshot for details.
Seems like the server edition is different.
I have added propriety on the closed status: jira.permission.comment.user denied, this closes the comments when the ticket is in the closed status.
After that i have created the automation rule:
See in server is different, as the first trigger, is not the same, we don;t have it as you have it on cloud.
This is what we have:
So now, without that, i can;t catch the comment with the automation rules, as there is no comment in fact, comments being closed.
Seems like there is no solution....or i don't see it.
I just tested again, so my findings are:
After a ticket is Closed, and the comments section is also closed - if a customer replies via email to such a ticket, a new ticket will be created with the title of the old one - but is not copying the description and is not linked back to the old one.
Looking at the automation rule the message is:
The automation rule i used looks like that:
So for me it seems like the automation rule is not even taking place - and my guess is the same as above, there is a slight difference between or "When" in the automation rules, is not the same and because of that is not triggering.
Hi Everyone, In this tutorial, we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached. SLA Threshold Trigger The SLA t...
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