I noticed that if someone uses to send email to open a new ticket but the subject of the email has already been used to open a ticket previously (which was then closed), it happens that the ticket is closed commented with the content new email, but it does not open a new ticket. It is a logical behavior, I agree, but some of you have experience on how to "circumvent the intelligence of users" and make sure that for example to open a new ticket if one already exists with the same object but closed?
(the second option that I have in mind, provides a penalty of 22 years in prison for those who should be implemented, for the moment I prefer not to apply ...)
Atlassian believes that 22 years in prison is a fairly light punishment for reopening closed tickets. We suggest you raise this punishment to at least 33 years, with no possibility of parole.
Serious answer is that this should not be happening in a default configuration. Is this just JIRA? Or do you have Service Desk installed? Are you using any third party mail handlers?
We have this issue as well and it's quite problematic. What we experience includes:
I think a simple solution would be if a new email is received and the existing Issue is not closed, it should attach itself to the Issue and proper notification will occur to the Assignee/status change will occur. If the Issue with same subject is already closed, Service Desk should open a new Issue.
This proposal does not solve the situation where a new email of the same subject is associated with an unrelated Issue, but it would at least ensure appropriate attention is brought where the issue remains open or results in a new Issue where it's closed.
I'm surprised this is not a more common issue.
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