A static archive of Markus Tacker's tweets. Follow me on Mastodon: @[email protected].
@lukehefson I'm sorry that I was not clear.
Here are my observations regarding abusing priority fields: a) Asana has a
free-text priority field, I worked in teams where we had priorities like A, AAA,
urgent, and my favorite: veryveryveryurgeng (I can try to find a screenshot).
@lukehefson This way is super confusing,
priorities need to have a clear (sortable) "rank".
b) Jira (and many others) have ranked priorities. But this gets quickly out of
hand, because new issues keep piling up and you can have an unlimited number of
issues with the same priority rank.
@lukehefson Now, if I make a list of all
issues and sort by priority, that list is totally useless in order to figure
out, which issue to focus on next, because there will be many issues that share
the same priority.
This is a broken way to rank issues.
@lukehefson That's why I want a forced ranking
of all issues, so that there is exactly 1 issue with the highest priority. If
you create a new issue and want to assign a priority the reported needs to pick
which issues are less important, and which are more important.
@lukehefson And this should ideally be applied
per-organization (in GitHub), or per project (in Jira speak).
@lukehefson Because what sucks even more is to
have to juggle priorities between different projects (in GitHub) or components
(in Jira). You have to mentally calculate: issue priority x value of project =
actual priority.