Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-3821

Priorities per Project and Resolutions per Issue Type



    • 8,247
    • 457
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.


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

      Atlassian Status as of 25 February 2019

      Hi everyone,

      Thanks for voting and commenting on this issue. I’m Nathan a Product Manager at Atlassian that is working on project configuration for next-gen projects.

      We have been working hard on simplifying project setup and configuration, as one of the Jira team's top priorities right now. We are making a big investment to make project configuration in Jira so intuitive, that anyone can do it. This is no small feat, given that we need to retain the power and configurability that our users expect.

      To do this we have been iteratively working on next-gen projects (formally known as Agility projects), starting with a simple experience and adding more powerful features as we go. I have been eagerly watching top voted feature request tickets like this for sometime and waiting for the opportunity to work on this feature. I wanted to update everyone to say that my team is actively envisioning what priorities and resolutions per project will look like in next-gen projects.

      Please don't hesitate to contact me if you have any questions or feedback.


      Nathan Sturgess

      Product Manager, JIRA Platform

      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.


        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



              684cb16ed833 Carol Low
              a52b60e989d4 Oliver Wihler
              4335 Vote for this issue
              1737 Start watching this issue