Automating Closure of All Child Issues When an Epic is Closed JMWE

[Ahmed Saci]

Hello Atlassian Community,

I'm facing a challenge in automating a part of our workflow in Jira and would appreciate any advice or solutions you might have. Our process involves creating an epic for each new project, which then gets associated with various child issues (tasks and stories) that represent different stages or aspects of the project. Here's a detailed breakdown of our workflow and the specific automation I'm trying to achieve with the Jira Misc Workflow Extensions (JMWE) add-on:

Workflow Context: Upon creating an epic (project sheet), users decide on the necessary steps, creating related child issues (tasks, stories) with their workflows. In the workflow of these child issues, there is a status called "Project Abandoned" to indicate the discontinuation of the project.

Current Automation: I've successfully set up an automation in Jira that automatically transitions the epic to a "Closed Project Sheet" status when any child issue is moved to the "Project Abandoned" status. This part works as intended.

The Challenge: While I can close the epic automatically, I now need to ensure that when this happens, all other child issues linked to the epic are also closed or transitioned to a final status, essentially marking the entire project and its components as completed or abandoned.

Objective: Automate the closure of all associated child issues (tasks, stories) when the epic is transitioned to "Closed Project Sheet" status, either due to a direct action or as a result of one child issue being marked as "Project Abandoned".

Questions:

How can I configure JMWE to close all other child issues related to the epic once it is closed or marked as "Project Abandoned"?
Is there a way to target all child issues (regardless of their current status) and apply a transition to close them, reflecting the project's abandonment in their respective workflows?
Given that child issues may have different workflows, is there a recommended approach to ensure a smooth transition for all related issues?
I'm looking for insights, examples, or any guidance on how to set up this level of automation within JMWE in Jira. Your expertise and suggestions will be highly valuable to streamline our project closure process.

Thank you very much for your support!

[Suprija Sirikonda _Appfire_]

Hi @Ahmed Saci,

For your requirement, add JMWE Transition issue(s) post-function on the Epic workflow, to transition all the child issues that belong to the Epic.

Steps: 

1. On the "Project Abandoned" transition of the Epic workflow, add a JMWE Transition issue(s) post-function
2. Select "Target issue(s):" as "Issues that belong to the current issue (Epic)"
3. Using "Transition Picker", select the desired transition(s) and workflow(s) of the child issues of the Epic.

I hope this helps!

BTW, I'm from Appfire, the vendor of JMWE app. A support ticket has been created in our support portal for this case: SUPPORT-166868. However, we couldn't add you as a reporter. We’d like you to sign up for our support portal here and let us know your username so that we can mark your ID as the reporter, and you will be able to access the ticket.

If the above solution doesn't work for you or your requirement is different, please feel free to share it on the support ticket.

Regards,

Suprija | Appfire