There are organisations whose data protection teams require the Jira administrators to "hide" (archive) the issues instead of deleting them. They have their reasons however a bunch of unwanted sub-tasks cannot be treated that way. Why? Should be easy to open that door?

+1

I would also like the ability to Restore Sub-tasks individually without having to Restore the parent task.

This also applies for Jira Cloud - even though the REST API is experimental currently, this is still how it's behaving. Sub-tasks should be archive-able.

This is annoying... moving sub-tasks in order to archive them- is there a simpler way to achieve that?

+1

We are getting a number of requests from our user base to be able to archive sub-tasks. Justification is that the time it takes to convert to a type that can be archived is time-consuming and disruptive to the workflow.

+1 for this.

Duplicate ticket enter for the same request JRASERVER-70161.

business justification  from https://getsupport.atlassian.com/browse/PS-53775

"Business justification for this is as follows:
Delete is like no go back but archival is considered as a recycling bin like a confluence trash to restore and which also improves performance as part of maintaining our instance we want to archive issues using archival rest call and archive anything which is older than 2 years to keep our instance clean and perform well in terms of indexing. Delete is considered little bit dangerous as you cannot restore the issue . So, Archival is what is driving this use case but we have seen that most of the users create sub-tasks as mistake which they want to remove or delete and it dosen't make sense as delete works with sub-task but not archive ? This is our use case and we want archive to work for sub-tasks."