My Ideal Scorecard

Here's what I think would be ideal for scorecards, using a RICE model:

1. Allow the user to select a text value that corresponds to the numeric score. This will help consistency across users and projects. So that a score for "Reach" might be expressed as "Few", "Many" or "All" instead of 1,2,3, and "Impact" would have values like "Differentiator" vs "Minor Usability"... as guidance.
   The work-around of using the text description to list the numbers alongside their meanings is clumsy and won't lead to consistency since that text isn't visible when you "Open Scorecard" and drag the sliders around.

2. Allow the scores to be non-integer. (There's another idea for this with 150+ votes)

3. Allow scorecard values to be shared between score fields. So that we can sort or rank issues by R*I*C/E, and also by just their "value" R*I. Like when E isn't known yet, or isn't relevant. I don't see a way to accomplish this today, perhaps there is one?

4. It is nice that the components of a score can be added individually to a list report. It would be helpful to be able to sync those individually to Jira too, where developers can see them.

5. Finally, a way to formally handle "Unknown" or lack of (C)onfidence or lack of information. Like an (E)ffort that you don't know yet. Currently, you can only do that with 0s, which makes the rest of the score 0 too, usually. I'm thinking of something like what spreadsheets do -- propagate the "unknown" through the calculation. Or better, indiciate "Unknown" but allow a default value which might be middle of the road, or might be a high value until the factor is proven lower, or vice-versa.
   This will reduce the temptation of making up a value which we can't later tell the origin of. If we don't know yet, let's mark it as such.

Thank you!