Jira Service Management Archiving practices

[Juul Weijers]

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?

[Adam Sterrie]

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.

[Liam Green]

Hi @Juul Weijers 

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:

https://jira.atlassian.com/browse/JSDCLOUD-1547?error=login_required&error_description=Login+required&state=abf1c9b5-3365-4ca3-9b34-b93d0c69981d

If you vote and watch that then hopefully it will be implemented.

Hope that helps,

Regards, Liam