What's the best way to track the pain level of my feature request/bug cards?

[Regina Bellows]

We are a SAAS company and we use Trello to keep track of bugs & feature requests. Some of these bugs/features are very painful for our customers (they prevent usage) and some are just "nice to have someday." There's a scale between those two extremes and I'm trying to come up with a way to help our product manager so he can sort through the most painful ones first. What's the best way to go about this?

[Regina Bellows · Accepted solution]

I've learned two ways to go about this:

1. Use the custom fields add on. It lets you create dropdowns. I created one for "User Priority" and one for "Dev Difficulty." The dropdowns are great and appear on the outside of the card, BUT they are not searchable or filterable.

2. If searching and filtering through these fields are super important, the only way I can think of doing it would be using the labels. These are like tags... So you'd have to create each option as it's own label. For example "User Priority 1 (low)" User Priority 2 (kind of low), etc.

[Shawn Masters]

Create criteria to check issues agiasnt then use something like a priority or severity field to assign a 'pain level' to the issue. We do this for our service desk as well. So when a bug is submitted depending on the submitted info the ticket is categorized as one of the following prioritries Project Low Med High