You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm trying to solve a problem in one of our projects. Our project involves many sub-task types used simultaneously under a base-level issue/story. My goal is to establish a rule that will prevent a status change on the base-level issue until all the sub-tasks of a specific type are in a "done" status category but will allow other sub-task types to be in varying status categories. I've been able to do this if ALL sub-tasks are "done" but not for just specific type(s).
Our instance does have scriptrunner. Are there any recommendations to solve our issue, or does anyone have experience doing the same?
Hi Mat! Here's a proposed solution.
1. Create a custom field named "Can Transition" with a default value of "True."
2. In the workflow for the "base-level issue," create a condition for all transitions that checks whether the value in the "Can Transition" field is "True."
3. Then, create a Jira Automate rule that sets the field to "False" if a new sub-task is created.
4. Create another rule that sets the field to "True" when all sub-tasks are closed.
Remember to set the correct value for the "Can Transition" field on existing base-level issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.