Currently you can only vote (for priority) after an issue got confirmed.
If a user reports an issue, it’s likely that this user also likes to vote for it. But the user would have to wait for confirmation and then visit the issue again to be able to vote for it.
Similar, if a user confirms an issue, this user might want to vote for it, too, but the user would also have to wait for confirmation first before being able to do this. As there is no list for issues you have confirmed, this means the user would have to remember the issue and remember to revisit it again.
Proposed solution:
- Allow voting for unconfirmed issues.
Benefits of the proposed solution:
1. Users don’t have to come back to issues just to vote for them (see above).
2. It becomes more clear that confirming an issue is not a way to vote for it. While an issue might be valid, it could be that you don’t like it. Currently many users use the confirmation feature to vote for issues (e.g., unconforming a valid issue because the user thinks it’s not important). Having both options (confirming / voting) at the same time makes the difference more clear.
1. Confirm (or create) an issue.
2. You are not able to vote for its priority until it got enough confirmations.
|
issue was resolved by TheKroko
|
| 0 players say this report is valid, 0 disagree |