I’ve been thinking about this a lot and I have some ideas:
We could have four levels of priority: low, medium, high, urgent. Urgent is red with a warning icon while the others are just gray and used for prioritizing. Then we can view the High Priority subcategory for a well-sorted todo list to do next.
I’m hesitant to mark threads with a level of progress like “ongoing”, “next up”, etc… Priorities shift a lot, so something that was marked as “next up” might get deprioritized but stay marked as “next up” unless we take time to periodic re-tagging. But I think if we use priority tags well, it could generally be assumed that urgent things would happen first, and high priority things will be happening next, etc… An “in development” tag could be good, especially since sometimes I have already fixed the bug but the update release is delayed by another task I want to get in the update, or if I fix it at night and want to wait until morning to release it.
I like the idea of tagging whether it needs reproducing, but at least for now most things have been easily reproducible or people already shared repro steps, so I think we should bias the other way and have a “Needs reproducing” tag.
Similar to reproducing, there’s some issues where the right solution isn’t clear yet and it needs further discussion. So we could have a “Needs discussion” tag for when we need more information before we can start working on it?
Since most discussion at this point is about desktop versions which are mostly consistent across web/mac/windows, and the mobile apps are generally consistent across iOS and Android, I think we should be good with just the one “Mobile” tag. Anything that’s not mobile is assumed to be desktop. I think adding more granularity there is not worth the effort, at least at this point.
The cosmetic/functional distinction is interesting, but I wonder if it would add too much complication over simple priority levels? In theory cosmetic issues should be lower priority and functional issues should be higher priority? But maybe some examples would help me understand how that distinction could be helpful?
Another possible set of tags could be for scope, as in how long development would take. There could be tags like Scope:small, Scope:medium, Scope:big. That would be hard for mods to know, but I could add them on my daily triage. And then maybe on some days we could work on a bunch of lower priority but small ones, so they don’t get left in the dust?
And another tag idea is “Popular” - Number of votes or comments should in theory bubble up the popular posts. And comments bring them to the top so they should be in our face a lot. But mods or I could make it more official by tagging as “Popular” because a lot of people want it. So then a bug/feature that is technically low priority but a lot of people want could get bubbled up.
That got long, so a summary of tags I’m proposing:
Pri:urgent, Pri:high, Pri:medium, Pri:low
Scope:big, Scope:medium, Scope:small
What do you think?