Essentially the same stuff as per:
How to avoid duplicate tickets due to changed subj... (atlassian.com)
I would love for some automation or some guidance on how to reduce the amount of tickets that the service desk gets from people cc'ing the service desk on these email chains that generate several tickets.
Ultimately, if it relates to the ticket, then add it as a comment.
However, this might not be the case and I'll need to do some tricky automation - as I also dont want users getting peppered with more emails saying that they've raised a duplicate request, its closed, heres a survey etc.
Hoping to get some sort of solid answer to this to help others looking for a similar fix when setting up their Jira service management environment for this type of issue as well.
@Fabio Racobaldo _Herzum_ - is this still something in the pipeline somewhere? maybe?
Thanks @mararn1618 _secretbakery_io_ , but I'd like to know what the rest of the community are doing on this. Or even from an Atlassian staff member to shed any light on this topic.
Yes, of course. I'm also curious of new approaches from the community / staff, so I'm following along.
---
If you ever change your mind:
https://marketplace.atlassian.com/apps/1224971/duplicate-ai-merge-similar-issues-duplicates
Hey @Phillip C, I just learned about customer organizations and request sharing and i think it could fix your problem. Already wrote about it here:
Let me know how it goes!
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Get started with Jira Service Management
These short, self-paced courses will help you get up and running in Jira Service Management in just 90 minutes.
Learning Path
Adopt ITSM practices with Jira Service Management
Use this path to build your IT Service Management knowledge and earn an Atlassian certification.
Setting Up ITSM Projects in Jira Service Management
This training series helps you get started in Jira Service Management quickly with the new ITSM project template.