Team,
As teams complete/close projects how do we go about archiving the boards/issues for future reference if needed (thinking audits etc).
Thank you,
Joe
If you have the Premium plan, there is a built-in Archiving feature: https://confluence.atlassian.com/adminjiracloud/archive-a-project-1013843066.html
If you are on Standard, you can use the "old school" way of archiving a feature: creating a permission scheme that limits browsing to just administrators, and switching "archived" projects to that scheme (effectively hiding it to regular users, but keeping it available for later audit purposes, etc.):https://confluence.atlassian.com/jirakb/archiving-a-project-in-jira-server-950287459.html
Darryl,
Thank you very much. We are currently on standard but looking at a premium plan. This is another feature we can add to our list.
Yes, this is the best way to archive on Standard version. I suggest naming the Permission Scheme to something like "Archived Project Permission Scheme" so it is easily referenced if new admins come on board they will understand what it is used for.
When is a good time to archive project? The link above shows that if the project is archived, then it won't be appeared in basic or advanced search results. However, our users sometimes would like to look back at an old issue for reference. How do we go about it?
@S Fong - what we do is do a search results export of all tickets from a project to a spreadsheet right before we archive the project. We then post the spreadsheet in Confluence. That will give users live links directly to the individual tickets, which do still work even for archived projects.
That's great to know. Do you find it easier to do what you mention above than keeping the project active? I am trying to understand the pros and cons between the 2.
For us, yes. We have 25 teams that each have several active projects, and if we keep them active just so they can reference them, the list of projects gets unmanageable. There will come a point where we archive the Archive project as well and start a new one; our agreed-on changeover is when the Archive project hits 30,000 tickets.
@Esther Strom Thank you! That is a great suggestion.
It looks like you're new here. Sign in or register to get started.
