Hello,
How can Jira automation be created to prevent Capability from closing until all child epics are not done or removed?
I tried some automation but it didn't work
Please help me to achieve this requirement.
Hi @Rajiv Ranjan ,
This can be achieved by using the Sub-Task Blocking condition in workflow.
You can also block the Sub-tasks from transition by using the Parent Status Validator (Validates that the parent issue is in required state).
Hi @Rilwan Ahmed
Sub-Task Blocking condition in workflow will not be valid for Epic as child issue issues, its only applicable for Sub-task.
We can achievable by Automation rule if you don't have any other Add On installed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Adding to the suggestion from @Rilwan Ahmed ...
Automation rules trigger after some event has happened. They cannot prevent the event from happening. And so a rule could not prevent the Capability from transitioning to "Done"...Instead it could only transition the issue back to another status, and perhaps send a notification.
To prevent the transition, you would need a workflow validator, possibly using a marketplace addon / app.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.