Uploaded image for project: 'JIRA Server (including JIRA Core)'
  1. JIRA Server (including JIRA Core)
  2. JRASERVER-3821

Priorities per Project and Resolutions per Issue Type


    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.


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

      Atlassian Status as of 7 September 2017

      Hi all,

      We're excited to announce some real progress on this issue!
      But first, thank you so much for all your votes and comments on this suggestion. You made it the most wanted feature suggestion on jira.atlassian.com. We appreciate your patience, and apologies for not giving you an update in such a long time. While we had explored solutions in the past, we hadn't come up with one that we could implement in a feasible manner, and without negatively impacting other areas of the product. This time we've approached it differently.

      We revisited this area with earnest again a few months ago to explore in more detail, how priorities per projects and resolutions per issue type could be incorporated into JIRA. In the process, we also asked some of you for additional feedback.
      We've looked at several options and believe the best approach for our Server customers is providing a Priority Scheme, so projects can have independent priorities, but also share the same priorities across projects. This solution will provide you with a well known administrative mechanism and still maintain a consistent experience.

      We're excited to share with you that we plan to add Priorities per Project to JIRA Software and Core in the near future.

      Resolutions per issue type is really a separate feature request which we'll prioritise independently. In order to track it properly, we've created a separate suggestion purely for Resolutions per issue type here: JRASERVER-65924.
      In hindsight we should have separated the two a long time ago, but we promise we will use all the comments around resolutions from this suggestion in the design of the feature, so no need to put the same comments, just make sure to vote and watch the issue! We will provide further updates in there.

      Thank you again for all your feedback on this suggestion and I look forward to providing you with more updates as we implement Priorities per Projects!

      Jakub Lazinski
      Product Manager, JIRA Server

      Original request description:

      As a JIRA Administrator I need more granular configuration for my projects:

      1. I want to be able to specify different priorities for different projects instead of having a global priority list. The current global priority can be used as a default, but I would like to be able to change them per project.
      2. Depending on the issue type, the resolution may be different. For example: in case of bugs, the resolution may be set to "fixed", but in case of improvements there is nothing to fix and the resolution should rather be "implemented". I need to be able to specify the default resolution separately per each issue type.

      Potential Workarounds:
      There are some workarounds that can provide some solutions to this issue:

      • Custom fields for priorities and resolutions can be used on a per-project basis.
      • Customizing velocity templates to limit the visible priorities and resolutions per project, similar to what's posted below (though this approach does not apply for JIRA Cloud customers).


        1. CvsR.png
          52 kB
        2. issue-create.vm
          6 kB
        3. MUSTNOTOK.png
          42 kB
        4. MUSTOK.png
          40 kB
        5. priority-edit.vm
          3 kB
        6. priority-edit.vm
          3 kB
        7. resolution-edit.vm
          3 kB

          Issue Links



              • Assignee:
                oliver.wihler@aqris.com Oliver Wihler
              • Votes:
                2538 Vote for this issue
                1209 Start watching this issue


                • Created: