I have an epic that creates multiple subtasks by default when it is created, then we create tasks that are linked to the epic as well. Is there a way to validate that certain subtask(s) are done before allowing an issue to transition using a custom field checkbox?
Epic 5 is created with 5 subtasks with standardized names
Issue 1 is linked to Epic 5 and requires subtask 1 and subtask 3 of epic 5 be finished before it can move along it's own workflow.
Issue 2 is also linked to Epic 5 and requires subtask 1 and subtask 4 and subtask 5 of epic 5 be finished before it can move along it's own workflow.
Please note that this is non-technical workflow and linking issues would be something that the users might not be able to do well or at all. So I would want to have a checklist ideally for them to saying task 1, task 2, task 3, is required for this to move forward and since the subtasks names are always the same, just check the epic's subtasks if they're done. All the subtasks are different workflows as well if that's important!
Thanks for reading!
I also want to say that different transitions require different restrictions. 1st transition would restrict if first checkbox is checked and subtask 1 isn't finished. 2nd transition would restrict if second/third checkbox is checked and subtask 2/3 isn't finished. and so on.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs