Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Prevent status change until sub-tasks of a certain type are "done"

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?

1 answer

0 votes
Dag Atle Stenstad
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 06, 2023 • edited Nov 09, 2023

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."

2023_11_10_08_25_14_Window.png

3. Then, create a Jira Automate rule that sets the field to "False" if a new sub-task is created.

2.png

4. Create another rule that sets the field to "True" when all sub-tasks are closed.

 

3.png

 

Remember to set the correct value for the "Can Transition" field on existing base-level issues.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events