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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,890
Community Members
 
Community Events
176
Community Groups

Prevent a blocked issue from transitioning until the blocker is 'Done' without script runner

Hello, I'm looking to prevent an assigned user from starting work on a blocked issue until the issue blocking it is completed.  Ideally, would want assignee A to complete the issue, and once the status is "Done/Resolved/Closed", this would notify the user of the blocked issue that they can begin work.

Is there anyway to do this in JIRA cloud, scrum board, without script runner? 

When creating a story, you have the option to link issues and determine which ones are blocked by which, but they seem to have no actual functionality (i.e. only informational to user; can still complete the other tasks first before completing the prior tasks that are "blocking" them from starting). 


example.PNG

Thank you! 

1 answer

1 accepted

0 votes
Answer accepted

Hi @Ashley Leger 

There's not a Workflow condition for this - but I can think of a workaround...

  • Create a checkbox custom field - such as Blocked?
  • Use Automation to populate/NULL this field - i.e...
    • If Issue A blocks Issue B, and A is open - populate Blocked?
    • If Issue A blocks Issue B, and A is closed - NULL Blocked?
      • This rule could also notify the user via an email or comment action that B is ready to be worked on
  • Set Value Field condition(s) on all possible transitions from the first Status - blocking the transition unless Blocked? is NULL

Do you think this would work for your scenario?

Let us know, or if you would like any more specific instructions for the above!

Ste

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events