nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Blocking Workflow Transition To Done if Linked Issues "Is blocked by" are not Done

Sebastián Delmastro

Any way to block issues transition on the Validators/Conditions/Post Functions workflows tools in jira to prevent the transition of an issue if it has any linked "Is blocked by" issue.

Linked issues can be any type and any project as we have several of them.

BTW we use Jira Cloud.

I am not looking for any add-on for the moment to solve this. Even Though we have automation for jira we are not looking to program post functions on this.

Thanks.

Accepted answers

somethingblue

Hi Sebastian,

This question has been asked a couple times and the end result is that you will need an add-on to accomplish this. See this article as well as the Suggestions for this titled Ability to prevent closing an issue if all linked "is blocked by" issues are not closed.

Please vote on the Server version ( JRASERVER-43369 ) and the Cloud version ( JRACLOUD-43369 )to add impact so we can get this added natively.

Cheers,

Branden

All comments

somethingblue

Hi Sebastian,

Please vote on the Server version ( JRASERVER-43369 ) and the Cloud version ( JRACLOUD-43369 )to add impact so we can get this added natively.

Cheers,

Branden

Sebastián Delmastro

Thanks @somethingblue for the quick response!

Vivek Agarwal_dx3ub7

Lot of people would have document this. I am not aware of groovy scripting. Can someone paste and example of the script which solves the upper mentioned issue.

Will help a lot. Thanks in advance!

Dave Macolino

Once again, something that should be included in base functionality isn't and requires a plugin.

Dale Sedivec

Note that, as far as I can tell, this is not possible with an add-on either, per se. I do not think Jira Cloud gives the ability for add-ons to implement conditions nor validators. Best bet would be a trigger (webhook) that reverts the issue's status *after* it has been changed. Which sucks.

See also this post from Adaptavist ScriptRunner folks where they explicitly say this is impossible.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-cloud

addon-com.codebarrel.addons.automation

transition

workflow