An alternative to Archiving a project while allowing Search?

[Josh McManus]

So my organization needs to maintain access to older tickets in order to find older bugs for products that may be End of Life. The problem with Archiving a Jira project is that none of the tickets within can be searched for after it's archived. I'm considering creating a Read-Only project that has all statuses and all issuetypes with a new field called "Original Jira Project" with the plan to move all tickets in projects I want to "archive" into this project while adding the original project to that field. The benefit of this is that it will dramatically reduce the number of projects in my instance and reducing the complication of administration tasks while allowing these tickets to be searchable...however I've realized I'm going to run into problems when it comes to Versions. Manually recreating every version that exists in the source project into the Archive project is going to be very labor intensive. Any ideas how to make this possible? Any alternative ideas (aside from Atlassian making Project Archival more useful)?

[Victor Law · Accepted solution]

Hi @Josh McManus

You may consider creating a READ ONLY project permission scheme with Browse Project permission only, which allows the issues to be searchable but NOT editable.

Thank you.

[Josh McManus]

I see, and otherwise migrate these projects to the same issuetype scheme and workflow scheme that allows all statuses and all issuetypes so i can start using a single workflow/issuetype/field config schemes for all "archived" projects and still minimize administration overhead and complexity. That does seem to achieve the same ends, with the benefit that if Atlassian ever implements https://jira.atlassian.com/browse/JRACLOUD-74992 then the projects will still be intact for better archival. Thanks!

[Laurie Sciutti]

I second @Victor Law's suggestion.  I do this and it works well.