JSM Archiving is not currently supported by Atlassian, as per their website: https://confluence.atlassian.com/adminjiracloud/archive-a-project-1013843066.html
However, we currently have old Jira Service Desk projects that are cluttering up our portal. These contain issues that need to be archived for audit purposes. What would you recommend we do in this situation?
An alternative/workaround could be to create a project in regular Jira (with the same workflow, statuses, versions, components, priority scheme), and then move all the tickets from the Service Management project to it. Then delete the Service Management project and archive the new one.
One option would be to remove the customers from the project - if a customer does not have access to a project then it won't appear on their portal.
Alternatively, there is a suggestion currently under consideration:
If you vote and watch that then hopefully it will be implemented.
Hope that helps,
Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...
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