Difference Between Archive Issues (New) and Archived Issues via a Release-FixVersion

[David Tieman]

What is the difference between the newly announced "Archive Issues" option and the function of Archiving a Release (FixVersion)?  I realize the association of Issues to a Release but what is the Use Case for these 2 options?  

Thank you

David Tieman

[Trudy Claspill · Accepted solution]

Hello @David Tieman 

Are you referring to this Archive An Issue feature?

https://support.atlassian.com/jira-software-cloud/docs/archive-an-issue/

Archiving an issue makes the issue invisible to searches. It is accessible only through a direct link to the issue. The issue also is then blocked from being updated. This can be useful for improving performance of searches and also for reducing the issue count in Boards and Backlogs to below the maximum 5000 issues limit.

Archiving a Release does not change the issues associated with the release in any way. Archiving a Release prevents you from adding/removing issues for that release. This is useful when you don't want anybody to be able to change the issues associated with a Release.

[Bill Sheboy]

Hi @David Tieman 

Yes, and...

Archiving a release / version is how you "hide" it from the dropdown lists for the Fix Versions and Affects Version fields, reducing clutter by not showing your released versions.

Kind regards,
Bill

[David Tieman]

@Trudy Claspill  & @Bill Sheboy  Thank you for your responses. 

Regarding the new feature of Archive Issues, is there any bulk method of moving issues to this Archive? 

Regarding the Archived Release and associated issues, when searching for issues we have still had those results appear in our Filters.  The Release was in a "Released" and "Archived" status.  I will test that again but I recall that result when last attempted in 2024.

Thank you

David Tieman

[Trudy Claspill]

Hello David,

It does not appear that Archive Issue is available in the Bulk Change feature nor in the Automation Rules feature. There is an experimental API for archiving a single issue, and you could write your own code or use an Automation Rule to call that repeatedly.

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-archive-put

Archiving a Release has no impact to the accessiblity of the issues associated with that release. It only impacts you ability to add/remove issues from that release, or find that release in Version type fields like Fix Version and Affects Version.