Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-13360

SHOULD be able to vote for resolved issues

XMLWordPrintable

    • 1
    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Problem Definition

      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.

      Suggested Solution

      Allow Admin to set a default setting so that there will be a global setting whether the Admin wants users to vote on a Resolved issues or not.

            [JRASERVER-13360] SHOULD be able to vote for resolved issues

            Steve Roughton added a comment -

            Unfortunately it's not even possible to override Jira's restriction on voting for resolved issues, because the restriction occurs in a private final method of the class jira.issue.vote.DefaultVoteManager.

            Is it possible to register a different VoteManager?

            Steve Roughton added a comment - Unfortunately it's not even possible to override Jira's restriction on voting for resolved issues, because the restriction occurs in a private final method of the class jira.issue.vote.DefaultVoteManager. Is it possible to register a different VoteManager?

            Neal Applebaum added a comment -

            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:

            (custom) Status Has Resolution? Allow Voting
            Open No Yes
            Resolved Yes No
            Deferred Yes Yes
            Closed - Voting allowed Yes Yes
            Closed - no voting allowed Yes No

            By default "Open" would have voting enabled, and any new status would not have voting enabled

            Neal Applebaum added a comment - 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: (custom) Status Has Resolution? Allow Voting Open No Yes Resolved Yes No Deferred Yes Yes Closed - Voting allowed Yes Yes Closed - no voting allowed Yes No By default "Open" would have voting enabled, and any new status would not have voting enabled

              Unassigned Unassigned
              0a1e1249fe05 Rob Lanphier
              Votes:
              21 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: