I would like to be able to run studies such as win/loss analysis on archived project/issues. Ideally, I'd like to be able to sort archived projects by custom data fields detailed in custom columns.
Can this be done now or is it in the works?
To add to Sergey’s answer, a tip for the future: if you need to report on finished projects, don’t archive them. Archiving is meant for decluttering, and it takes the data out of search and reporting.
Instead, keep them active and mark them as done. Use a project category like “Closed” and restrict permissions so nobody can edit them anymore. Then you can still use JQL, filters, dashboards and CSV exports with all custom fields, e.g. category = Closed, and build your win/loss view directly in Jira.
category = Closed
Hi Joshua,
If you’re using Jira Cloud and the win/loss data is stored in issue custom fields, one practical workaround is to restore the relevant projects/issues and export the data for analysis.
There are two important limitations:
For a one-off analysis, you could:
This gives you an analysis outside Jira; it does not add custom columns or sorting to the archive screen itself.
Are you using Cloud or Data Center, and are those custom fields attached to individual issues or to the projects themselves?
Not natively today. Work items in an archived project (space) don't appear in basic or advanced search, so JQL, filters and dashboards can't report on them. They only open read-only from a direct link. Individually archived work items appear only in the Archived work items list. There is a suggestion for read-only access to archived project work items without restoring them, JRACLOUD-74992. It's still Gathering Interest, so vote and watch it: https://jira.atlassian.com/browse/JRACLOUD-74992
What works now:
If your win/loss data belongs to the project rather than its work items, Project Charter is an app we build for project-level portfolio data. You define properties like Outcome, Value or Close date once and fill them in on every project. You can then review them as columns in a list view with filters and Excel export, or in dashboard gadgets: https://marketplace.atlassian.com/apps/1226357/project-charter
Adding to Pavel's tip, because it decides whether you can report on old projects later: native archiving takes the work items out of search, so for anything that is already archived you need to restore first, as Sergey and Mertcan described. For the future, the permission-based route Pavel suggests keeps the data reportable.
Disclosure: I built an app that takes that route for you, Project Archiver for Jira. Archiving a project switches it to a read-only permission scheme, an empty notification scheme, the category "Archived" and an "[Archived]" name prefix. Everyone else stops seeing it in project lists, search and boards, but the project lead and the project's Administrators role still can, so for them JQL (for example category = Archived), filters and CSV export keep working with all custom fields. Restore puts the original name, schemes and category back in one click, and every action is logged with a reason.
Limits: company-managed projects only, the analysis has to be run by someone in that role, and it doesn't change projects you have already archived natively. Free for up to 10 users: https://marketplace.atlassian.com/apps/578576872
It looks like you're new here. Sign in or register to get started.