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

Priorities per Project and Resolutions per Issue Type

    • 74
    • 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.

      Atlassian Status as of 17 November 2017

      Hi everyone,

      We're excited to announce that Priority schemes were just shipped with Jira Software 7.6. As some of you have already noticed, 7.6 was released yesterday, and you can download it here.

      What we've built

      As mentioned in our previous update, after research, spikes, and user interviews, we've decided that introducing Priority schemes is the best solution for our customers. This feature uses a well-known administrative mechanism, and maintains a consistent experience.

      Further improvements

      We've put a lot of effort into delivering Priority schemes as early as possible to make it for the 15th anniversary. We've decided that some further improvements will be added after the Jira 7.6 release. These will include: REST APIs to manage priority schemes, the ability to copy the priority schemes, as well as some minor UI improvements. We're planning to release them in the following Jira version (most likely 7.7).

      Jira Service Desk

      We've been working closely with the Jira Service Desk team to understand the impact of Priority schemes on customers using Service Desk projects. We wanted to make sure that these customers receive the best experience when Priority schemes are introduced.
      To achieve this goal, we've identified further work, and are scoping it specifically for Jira Service Desk.
      To make this feature available for Jira Core and Jira Software customers as quickly as possible, we've decided to release it without the support for Service Desk projects. What it means is that admins will not be able to associate a priority scheme with a Service Desk project in the first version.
      This capability will be released independently by the Jira Service Desk team. Tracked in JSDSERVER-1374

      Resolutions per issue type

      We're re-adding the previous update on Resolutions per issue type here so that it's not lost in the stream of comments on this suggestion.
      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.

      You can read more details regarding Priority schemes and other capabilities that we added in Jira Software 7.6 here.
      As always, we would love to hear your feedback so feel free to reach out to me directly, or post a comment in this suggestion.

      Cheers,
      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
          CvsR.png
          52 kB
        2. image-2018-02-21-17-48-17-549.png
          image-2018-02-21-17-48-17-549.png
          14 kB
        3. image-2018-05-17-08-09-27-721.png
          image-2018-05-17-08-09-27-721.png
          4 kB
        4. issue-create.vm
          6 kB
        5. MUSTNOTOK.png
          MUSTNOTOK.png
          42 kB
        6. MUSTOK.png
          MUSTOK.png
          40 kB
        7. priority-edit.vm
          3 kB
        8. priority-edit.vm
          3 kB
        9. resolution-edit.vm
          3 kB

            [JRASERVER-3821] Priorities per Project and Resolutions per Issue Type

            Hi!

            I have a problem with 7.8.2: I cannot see the Priority Schemes link under Administration -> Issues -> Priorities (See my attachment).
            Any idea how to get the feature to work?

            Regards,

            Davide.

            Davide Trombini added a comment - Hi! I have a problem with 7.8.2: I cannot see the Priority Schemes link under Administration -> Issues -> Priorities (See my attachment). Any idea how to get the feature to work? Regards, Davide.

            Hi rydh,

            Please follow JRACLOUD-3821 for similar updates for Jira Cloud. We are working to address the same problem in Jira Cloud, although the solution provided may be different than what has been shipped to Jira Server. See my comment from November 2017.

            Regards,
            Dave

            Dave Meyer added a comment - Hi rydh , Please follow JRACLOUD-3821 for similar updates for Jira Cloud. We are working to address the same problem in Jira Cloud, although the solution provided may be different than what has been shipped to Jira Server. See my comment from November 2017 . Regards, Dave

            Hi!

            Is this ticket ever going to make it to Jira Cloud? I have been trying to find help with this particular issue for Cloud, but searching anything returns a saturated history of Jira Server related discussions. Any advice would be greatly appreciated!

            Thanks

            /Fredrik Rydh

            Fredrik Rydh added a comment - Hi! Is this ticket ever going to make it to Jira Cloud? I have been trying to find help with this particular issue for Cloud, but searching anything returns a saturated history of Jira Server related discussions. Any advice would be greatly appreciated! Thanks /Fredrik Rydh

            Loving the functionality.

            Any chance I can get the notification message to actually dismiss though

            Link 'Dismiss this warning' does not work, and the X just means it is going to return to haunt me...

            Richard Crampton added a comment - Loving the functionality. Any chance I can get the notification message to actually dismiss though Link 'Dismiss this warning' does not work, and the X just means it is going to return to haunt me...

            Tomasz Kanafa added a comment - - edited

            mrkalle76 Thank you for your feedback.

            All newly added priorities end up in default priority scheme is because it was designed this way for backwards compatibility which is very important for vast majority of our customers.

            We didn't want to change existing behaviour where all new priorities were available to all projects hence this behaviour.

            To resolve your problem you could clone existing default priority scheme and assign all projects using default priority scheme to the newly cloned one - after that even if new priority will be added to the default priority scheme it will not affect other projects. 

            Cheers!

            Tomasz Kanafa added a comment - - edited mrkalle76 Thank you for your feedback. All newly added priorities end up in default priority scheme is because it was designed this way for backwards compatibility which is very important for vast majority of our customers. We didn't want to change existing behaviour where all new priorities were available to all projects hence this behaviour. To resolve your problem you could clone existing default priority scheme and assign all projects using default priority scheme to the newly cloned one - after that even if new priority will be added to the default priority scheme it will not affect other projects.  Cheers!

            Karl Petersson added a comment - - edited

            Thanks for implementing this feature.

            I found the following issue with the priority Scheme:

            When I created new priorities they become available for users due to the fact they where added to the default scheme with no possibility to remove them. I found this bad since during the time I added a numeric priority scheme users used the new priorities which was not planned for them. I needed to make a new scheme with the default priorities and apply that for all projects.

            This could be improved but I’m happy to see an improvement in this area .

             

            What I would like to see is  that you can create new Priorities without beeing added to a Priority Scheme and The Deafault Priority Scheme shall be able to change.

            Karl Petersson added a comment - - edited Thanks for implementing this feature. I found the following issue with the priority Scheme: When I created new priorities they become available for users due to the fact they where added to the default scheme with no possibility to remove them. I found this bad since during the time I added a numeric priority scheme users used the new priorities which was not planned for them. I needed to make a new scheme with the default priorities and apply that for all projects. This could be improved but I’m happy to see an improvement in this area .   What I would like to see is  that you can create new Priorities without beeing added to a Priority Scheme and The Deafault Priority Scheme shall be able to change.

            Regarding "Resolution" part of the topic, I could suggest the following roadmap
            1. Add to all default vanila workflows the transition property at each green transition with resolution screen. jira.field.resolution.include = <list of default resilution ids>
            (this will help at the beginning, because most of custom workflows are cloned from the default)

            2. Extend GUI of Jira workflow editor to be able to configure the property in user friendly way (as multselect list of resolution names)
            3. Add resolution schemes and enable Jira worklow editor to switch between multiselect list of resolutions and the scemes. 

            The schemes will be then not on issuetype level but rather on transition level. Which  is more flexible, in fact  

            Gregory Kneller added a comment - Regarding "Resolution" part of the topic, I could suggest the following roadmap 1. Add to all default vanila workflows the transition property at each green transition with resolution screen. jira.field.resolution.include  = <list of default resilution ids> (this will help at the beginning, because most of custom workflows are cloned from the default) 2. Extend GUI of Jira workflow editor to be able to configure the property in user friendly way (as multselect list of resolution names) 3. Add resolution schemes and enable Jira worklow editor to switch between multiselect list of resolutions and the scemes.  The schemes will be then not on issuetype level but rather on transition level. Which  is more flexible, in fact  

            Hi kamil.wielocha1865935991,

            Please see my comment on JRACLOUD-3821.

            Regards,
            Dave Meyer
            Jira Cloud Product Management

            Dave Meyer added a comment - Hi kamil.wielocha1865935991 , Please see my comment on JRACLOUD-3821 . Regards, Dave Meyer Jira Cloud Product Management

            Hi,

            Is this functionality also planned for Jira & Service Desk Cloud? If so, please advise on estimated dates.

             

            Many thanks,

            Kamil

            Kamil Wielocha added a comment - Hi, Is this functionality also planned for Jira & Service Desk Cloud? If so, please advise on estimated dates.   Many thanks, Kamil

            Hello All,
             
            We are aware that the ability to associate priority schemes with Service Desk projects is important and expected by JIRA Service Desk customers.
             
            The good news is that this is definitely one of our priorities right now and we're exploring ways to make this available at the earliest in Jira Service Desk. Whilst I’d like to give you a clear timeframe for when we can deliver this, unfortunately, I cannot make such indications yet.

            In order to make it easier for Jira Service Desk customers to track the progress of this effort, we've created a separate JAC issue which you can watch, vote and comment on. You can find it here: JSDSERVER-5513
             
            Thanks again for your patience,
             
            Vidhu Sharma
            Product Manager | JIRA Service Desk

            V (Inactive) added a comment - Hello All,   We are aware that the ability to associate priority schemes with Service Desk projects is important and expected by JIRA Service Desk customers.   The good news is that this is definitely one of our priorities right now and we're exploring ways to make this available at the earliest in Jira Service Desk. Whilst I’d like to give you a clear timeframe for when we can deliver this, unfortunately, I cannot make such indications yet. In order to make it easier for Jira Service Desk customers to track the progress of this effort, we've created a separate JAC issue which you can watch, vote and comment on. You can find it here: JSDSERVER-5513   Thanks again for your patience,   Vidhu Sharma Product Manager | JIRA Service Desk

              Unassigned Unassigned
              a52b60e989d4 Oliver Wihler
              Votes:
              2570 Vote for this issue
              Watchers:
              1176 Start watching this issue

                Created:
                Updated:
                Resolved: