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

Priorities per Project



    • 14,810
    • 535
    • 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 11 May 2023

      Hi everyone,

      We’ve wrapped up the customer research study which was very insightful and thanks for everyone’s continued interest and valuable feedback on this ticket.

      We’ve also completed our technical investigations and will start implementation this month. We’ll be working towards an Early Access Program and will provide more details when we are ready.

      Please feel free to reach out with any questions.


      Nicole & the Atlassian team

      April 2023

      Hi everyone,

      We are doing further research on this topic and would love to invite you to take part in an upcoming customer research study!

      What’s involved in the research:

      • Sessions are 1 hour and conducted over video-conference, so you can participate from anywhere around the globe.
      • During the research, we'll start with a general chat to get to know you, then, you might explore a prototype and complete some tasks.
      • As a token of our appreciation, you'll receive an e-gift card within 5 days of completing your session.

      If you're interested in taking part, please complete this survey and we will get back to you. We’re testing with a small group to begin with and there will be chances to give more feedback in the future.

      If you have any other questions at all, please email me directly on nschwartz@atlassian.com. We look forward to meeting you!


      Nicole & the Atlassian team

      February 2023

      Hi everyone,

      As mentioned previously, we have now started onboarding a team (in Q1) to work on Priorities per Project, and have started analysis and early technical investigations. We are currently aiming to have high level estimations and timelines by the end of March. We appreciate your patience, and as the team ramps up, we will be able to provide updates more regularly.

      Finally, we’re also planning to hold research sessions in March - so please join our focus group (see details below) if you are interested to participate.


      Carol & the Atlassian team

      November 2022

      Hi everyone,

      Thank you for your continued interest, insightful feedback, and votes on this ticket. We apologize for the lack of update on this as we’ve been focussed on ensuring our cloud environment is performant at scale.

      To track the progress of this ticket more effectively, we’re updating this ticket to be "Priorities per project" and created a new ticket: JRACLOUD-80093 (Resolution per Issue Type) to track it as a separate feature. We are marking Priorities per project as our first focus from what we’ve heard from you through the comments you’ve shared, and will move it to “In Progress”. We’ll continue monitoring the interest for Resolutions per Issue Type

      Update on Priorities per Project:

      As part of a larger initiative to improve the way fields can be configured, we are planning to bring the ability to configure field contexts for Priority, Description, and potentially other system fields. We believe this unlocks multiple use cases we’ve heard from you - e.g. allowing for different default priorities per issue type, multiple contexts for custom fields per project, default values for description fields.

      These fields are core in Jira and we will be spending time to make sure the changes we make carry through all experiences in Jira smoothly. We have started planning and design work for this and will be onboarding a team to work on it from Q1 next year, and I will provide periodical updates on this ticket.

      For customers migrating from Server, we will look into providing a migration pathway from data in Priority schemes to field contexts.

      While we’re building this ability for you to have more control over key fields, we welcome you to join our focus group and work with us to improve configuration experiences in Jira. If you are interested, please email me at clow@atlassian.com and I’ll share more details on the group.

      Please feel free to reach out with any questions.


      Carol & the Atlassian team




      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
              4991 Vote for this issue
              2078 Start watching this issue