Archiving Sub-task issue type independently in Jira Software

[Drew Vaive]

Currently in Jira Software, when an analyst is creating subtasks for a specific User Story, Occasionally, an analyst will mistakenly create twice, as a duplicate. 

To keep the User Story as clean as possible, and to continue to utilize the Project List in its collapsable format, IE , not applying filters, which breaks the collapsable.

we would like a way to properly archive these Duplicate Subtasks, instead of deleting them. for record keeping and arching purposes.  I do see a previous Article from 2022 where someone named "Nic Brough -Adaptavist-" was dismissive of the use case presented back then and since then no further mention of archiving of these subtasks has been mentioned.

being able to keep our list in the collapsable view, only displaying active epics, stories and subtasks without a filter, and properly archive epics, stories , and subtasks is not currently possible.

currently what we do when this occurs is just create a "dummy" issue alongside the story that the analyst is aware cannot be deleted, archived, and it just clutters up our view,

we can cancel this issue, but then when filtering out cancelled the collapsable features of epic> story> subtask breaks. which is not ideal.  Can someone besides Nic shed some light on my use case!

[Swathi Acharya]

Hello @Drew Vaive

Good day!

Welcome to Atlassian Community!

As @Staffan Redelius has mentioned, the Archive feature is only available on Premium & Enterprise licenses.

At the moment, archiving the subtasks independent of the Parent work item is not possible in Jira Cloud. There is a Feature Request in place for the same: https://jira.atlassian.com/browse/JRACLOUD-94782

Thank you!

[Staffan Redelius]

Hi @Drew Vaive and welcome to the community!

Archiving work items is a Premium feature unfortunately and by the tags in your post you seem to be on Standard.

I understand this will clutter your view and the only solution I can think of is to re-assign the subtask to a dummy work item in another project if you still want to keep it but not have it visible in your current project.

You could also restrict the "delete" permission to a small number of users/roles if it is acceptable to delete the issues after investigation and confirmation that it really is a duplicate with no additional valuable information.

Best regards,
/Staffan