is blocked really a priority?

[John Stanford]

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?

[Nic Brough -Adaptavist- · Accepted solution]

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)

[John Stanford]

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

[John Stanford]

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.

[Renjith Pillai]

How is this related to GreenHopper?