As a Jira administrator, I frequently see this problem: child issues are closed but nobody remembered to close the parent issue. Users have already moved on to the next thing and the parent issue sits in its incorrect status forever. Or maybe it's the opposite: the Epic is closed, but its Stories, Bugs, and Tasks were forgotten.

When issue status does not reflect reality, reporting is a nightmare. All completed or unneeded issues should be transitioned to their final status. Why not take this step off your user's "to do" list and automate it? It's easy to automatically transition issues with Innovalog's Jira Misc Workflow Extensions (JMWE) app.

Use Case: When all child issues are closed, automatically transition the parent so users don't need to do it manually. Example: When all Sub-tasks are transitioned to the "Closed" status, automatically transition the Task issue to the "Closed" status.

 
You can also read/download this PDF document.

We know you have ideas on how to make your Jira workflows better, and we hope Jira Misc Workflow Extensions (JMWE) and Jira Misc Custom Fields (JMCF) help you do that.  Take a few minutes [updated 6/17/2019 - raffle closed] share how you use JMWE or JMCF and we'll share it with the world (we will respect anonymity if you prefer). Not sure how it would look? Just take a look at these real-life use cases already shared by other Jira superstars.

The major changes that Atlassian is making to the Jira REST API on top of which all apps are built, including JMWE for Jira Cloud, will impact some or all of your workflows. Though GDPR compliance was the primary reason for the changes, they will affect customers across all countries, not only those located in the European Union.

Starting on April 29th, in a continuous effort to improve customer trust and address all EU General Data Protection Regulation (GDPR) requirements, Atlassian is making very important changes to Jira Cloud that will affect (break!) some of your workflows. This affects all Jira Cloud customers.