As anyone using Jira Service Desk will I'm sure have experienced, if you have an "open" email address that anyone can email you get a certain amount of spam and other non-ticket stuff (I'm going to refer to tickets here, rather than issues, but I'm talking about tickets that exist in Jira as issues). These tickets then have to be closed off. In our case we transition them to Cancelled with a Resolution status of "Not a Ticket".
The problem with this is that over time you get a lot of these and they make it harder to find stuff when searching. I've been mulling over the best solution to this and this is my idea, would like to see what others think:
1. Create another project as a clone of my main service desk project and call it something like "Ticket Archive"
2. Set the permissions of Ticket Archive so that most users can't view it (so the contents don't show up in search results).
3. Periodically use the Bulk Edit feature to move the "not a ticket" issues from the main service desk project to Ticket Archive
The main downside to this is that changes to the structure of the main service desk project would need to be replicated in the Ticket Archive project (new fields etc) to ensure that the issues could continue to be successfully moved over.
Does anyone have any further thoughts on this as a solution, a better solution, or other potential issues with this approach?
Hi Jira Service Desk community, Atlassian is on a mission to unleash the potential of all teams, and we know that tools are just one piece of that puzzle. With Jira Service Desk, we have productiv...
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