Solving blocking issue should reopen blocked ticket

When ticket A is blocked by B, and ticket is B is somehow fixed/closed/rejected ticket A should be unblocked.

Why it is not and we need to check blocking tickets manually?


1 answer

Because each JIRA Project have their own requirements and putting restrictions by default and assuming everyone wants that is bad design.

Is there any way of automating what Tomasz wants?

/me makes script-runner noises.

It needs a bit of code in a listener or post-function that can pick up the particular events where something should be done, iterate over the links (assuming that's how the  blocks are being represented in this particular case), and examine the other ends to unblock them (and that could be a field or a transition itself)

Gabrielle is spot on as usual.  There are so many different ways you could be representing "blocks", there's no way you could anticipate and code for every single case.  So you need to find/write the code to support your particular implementation.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,647 views 18 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you