Block or limit ticket archive if child elements not archive

[Sylvain GROUSELLE]

Dear team,

By any chance is there a way to alert user if user try to archive a ticket with child elements not archived.

Kind regards

[Sylvain GROUSELLE · Accepted solution]

many thanks you're right, sorry for my mistake

[Gor Greyan]

Hi @Sylvain GROUSELLE

If one of these answers was helpful for you, kindly ask you to accept it.

Regards,
Gor

[James Bennett]

I think an alert before archiving would be a useful safeguard, especially when the parent ticket has child items that still need to be archived. Jira already handles subtasks differently when a parent is archived, but other child relationships may not be handled automatically.

A simple confirmation such as “This ticket has X active child items. Continue archiving?” would prevent accidental incomplete archives. It could also provide a list of the affected child tickets so the user can review them before proceeding.

This would be particularly helpful for teams managing large ticket hierarchies where it’s easy to overlook a child item. A small warning could prevent a lot of cleanup later. pbskidsgames.us.com can be a quick break between admin tasks.

[Gor Greyan]

Hi @Sylvain GROUSELLE

Welcome to the Atlassian Community!

It depends on what you mean by child elements.

If you mean subtasks, there is no need to block the archive operation until they are archived first. Jira doesn't allow subtasks to be archived independently; when you archive the parent work item, its subtasks are archived automatically.

If you mean child work items under an Epic, Jira Cloud now gives you the option to archive the Epic's child work items as part of the archive operation.

When you archive the Epic, you get the question if you want to archive the child issues as well.

Regards,
Gor