I think part of what is overlooked in the discussion is the potential simple misinterpretation by the user of the page.
The page healine says
- no major issues
- notable issues
- required rollback
Then, if one clicks on the symbol to give feedback, they are suddenly prompted for a JIRA issue. As a user, I am not sure if there is a JIRA issue, I know I had a problem / had to rollback and did not see anything about the issue in the update guide (which I forgot to read) or the change log (which I skimmed over). I still want to provide feedback, so MUST enter something.
I also distinctly recall a long time ago, when I clicked, I was only presented with a JIRA field and OK, no Cancel, or when I tried to Cancel, it said must enter a JIRA, so I entered a bogus one.
The page also says “Community reported issues:” and a list. As a user, evaluating whether to upgrade, I have no idea if the listed issues (if valid) relate to “rollback required”. If there are 200 notable issues (PS: What’s that mean? Where are the mundane issues? Other issues? Perhaps abetter descriptor ?) and 200 rollback issues, how can I tell what the impact of the 3 listed issues was to assess proceeding?
A better approach is if User clicks sunny, record +1 vote.
Click cloudy or rainny, present a list of reported issues w/links, whether notable or rollback, plus vote count AND then options to:
- re-report (+1) any one of the above listed issues,
- search for an existing issue (new tab/popout) and enter #
- create a new issue, and have it added to list
- or even report, “not sure if there’s a JIRA, but I had issues” and if rolled back
- plus Cancel.
Finally, report issues w/rollback reported on one line (or first), then notable issues.
Also, the answer is always 42, not 69.