Try adding a couple more dimensions, each rated on a scale of 1-3 or 1-5 or so: A field for number of users (or $ in contracts) affected (for instance, does it

Try adding a couple more dimensions, each rated on a scale of 1-3 or 1-5 or so: A field for number of users (or $ in contracts) affected (for instance, does it affect every single user for every interaction; or only enterprise users with the Foo setting on "bar" when the moon is full?) A field for severity/impact (Direct impact on cash flow? Data loss? Can't use the feature at all? Open up new markets? Decreased feature functionality? Significant bug with workaround? Minor bug?) A field for centrality of the affected feature (whole purpose of the product? Important to most people's workflows? Peripheral feature that only adds minimal value?) A field for complexity / level of effort to fix (rate this one on an inverse scale so that the highest numbers are the easiest to fix). A field for urgency (is there an external deadline attached to this? A vague manager expectation? Is the expected completion time next week? Next year?) For each ticket, multiply those numbers together, and you'll get a pretty decent and comparatively granular ROI ranking.