We can now archive a Confluence space, but we would also like to archive the associated JIRA project (not just the versions). Is there a way to do this or on the roadmap to do so as to align with Confluence and minimize confusion to users when viewing their project list (existing in JIRA but not in Confluence)?
Not yet - the best you can do is swap the project to a read-only permission scheme and minimise the usage. Just need to remember that if you limit "browse", then the project will be completely invisible to anyone without "browse"
I do however know that Atlassian are working on a more robust archive - aimed at their larger and older customers who have lots of dead issues, but need to retain some access to them, without compromising the performance etc of the more active data in Jira.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs