is blocked really a priority?

What happens to the historic priority of an issue when you change a ticket to blocked -- does it become irrelevant/lost or are blocked and priority really orthogonal?

3 answers

1 accepted

0 votes
Answer accepted

The current priority is the thing that matters.

The historical priority is in the history, but doesn't affect the current position. Blocked is really just a label, it doesn't do much special (unless you code something to do so)

Thanks for clarifying where I can get the historic priority. I unfortunately conflated two concepts: "Is blocked really a state?" and "how to I get the historic priority".

How is this related to GreenHopper?

In GreenHopper 6.1.2 for both Kanban and Scrum issues, the concept of blocked appears to be implemented as a value for priority ("Blocker"). This seems like a mismatch since something that was high priority before being blocked is probably still high priority, but to convey the message that it is blocked, I've got to give up it's actual priority and use that field to convey the state that it is in. When it becomes unblocked, I apparently need to dig through the change history of the issue to recall the actual priority -- clunky.

A better approach (in my opinion) would be to add a state for Blocked and slide the issue into that state while maintaining it's actual priority.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 13, 2019 in Marketplace Apps

Marketplace Spotlight: Marketing apps for Confluence to keep your teams working on the same page


263 views 0 6
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