| Key: |
JRA-13360
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Rob Lanphier
|
| Votes: |
7
|
| Watchers: |
8
|
|
|
|
Issue Links:
|
Reference
|
|
This issue relates to:
|
|
JRA-188
Shouldn't be able to vote for resolved issues
|
|
|
|
|
|
|
|
According to JRA-188, voting on resolved issues was taken out. However, this is a really useful feature in our installation for at least two reasons:
1. We use voting as a peer review mechanism, and highlight high vote issues come review time. This creates a bad incentive to leave votes open longer than they should
2. In our public JIRA install, we'd like to still collect votes on issues we marked "resolve/wont fix", so that we can reconsider should there be a popular groundswell.
|
|
Description
|
According to JRA-188, voting on resolved issues was taken out. However, this is a really useful feature in our installation for at least two reasons:
1. We use voting as a peer review mechanism, and highlight high vote issues come review time. This creates a bad incentive to leave votes open longer than they should
2. In our public JIRA install, we'd like to still collect votes on issues we marked "resolve/wont fix", so that we can reconsider should there be a popular groundswell. |
Show » |
Sort Order:
|
Here's my use case.
We have a development project with a custom workflow transition "Defer" that marks an issue as Deferred. That way it doesn't show up on our to-do lists. However, I still want our clients to be able to vote on these deferred issues.
Sounds like we need a scheme that maps Voting to statuses. If I could map voting to status I could say:
By default "Open" would have voting enabled, and any new status would not have voting enabled