Open Stack

Doug Hellmann wrote:
> I think we need to reconsider that position if it's going to block
> adoption. I think Ben's case is an excellent second example of where
> having a field to hold some sort of priority value would be useful.

Absence of priorities was an initial design choice[1] based on the fact 
that in an open collaboration every group, team, organization has their 
own views on what the priority of a story is, so worklist and tags are 
better ways to capture that. Also they don't really work unless you 
triage everything. And then nobody really looks at them to prioritize 
their work, so they are high cost for little benefit.

That said, it definitely creates friction, because alternatives are less 
convenient / visible, and it's not how other tools work... so the 
"right" answer here may not be the "best" answer.

[1] https://wiki.openstack.org/wiki/StoryBoard/Priority

-- 
Thierry Carrez (ttx)