nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why would you archive a product version?

Karie Kelly1

Could someone tell me why I would archive a JIRA project version? I was hoping it would minimize search results (e.g. you could not find an issue in an archived version) as this would make search results more relevant. But, it doesn't do that. I'm struggling with why it would be important to use this feature.

Accepted answers

Jobin Kuruvilla [Adaptavist]

When you create or edit an issue in the project, archived versions won't appear in the list. It just prevents users from using the version once archived.

You will still be able to search issues using archived versions because some issues already has that value on it.

All comments

Jobin Kuruvilla [Adaptavist]

When you create or edit an issue in the project, archived versions won't appear in the list. It just prevents users from using the version once archived.

You will still be able to search issues using archived versions because some issues already has that value on it.

Karie Kelly1

Thanks. I had hoped there was a way to reduce the searching...but, guess not.

It's interesting, though, with Tempo. Tempo will not pull in time on issues associated with an archived version...learned that the hard way when trying to pull some reports for finance.

Melanie Wu

This solution isn't really ideal, but you could create a secondary project and move those issues into it and archive the project. But you'll have to unarchive it to add more to it if you want, etc.