We are using JIRA Cloud. We Want a validator for an Epic to transition to Done only if all children are Done or Canceled.
- Epic should not allow transition to Done if I have a child ticket In Progress.
- Epic should move to Done if all children are either Done or Canceled.
We used a Validator, and it does not work.
Hi @Jyoti Patel
For this exact case our team developed the Linked Issues Validator available as part of the Workflow Building Blocks for Jira app. With a wizard-like UI, you can select options that represent your case. You can choose relations from: sub-tasks, parent issues, epic children, and linked issues. Additionally, you can filter relations by issue types and select criteria based on status category and status.
Our validators have a Jira expression preview feature, which can help you learn the correct syntax. This is how it looks for your case:
Probably the only fix you need is changing issue.children.every to issue.childIssues.every.
Full disclosure: I am from Forgappify, the vendor of the app.
Cheers
@Maciej Dudziak _Forgappify_ question for you regarding the app. Is the "Linked Issues Validator" run after the user clicks the submit/transition button, or does it prevent you/not showing the transition until the child work items are fulfilling the condition?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The app comes with both:
Condition hides the transition, validator prevents the transition (also create) and prompts user why the issue cannot be transitioned
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jyoti Patel,
What you are looking for is a condition, not validator. Conditions prevents users from transition work items if the condition is not fulfilled. Out of the box Jira only have a condition that can block the transition depending on the status of sub tasks. In order to do it based on issues linked to an epic you need an app from the Marketplace in order to do this. At a previous job I used scriptrunner to do this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Mikael. Appreciate the quick response.
We are using a JMWE (JIRA Misc Workflow Extenstions). We created the following. But either a logic issue or something....
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.