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

Provide the ability to edit the default priority scheme

XMLWordPrintable

    • 32
    • 34
    • Hide
      Atlassian Update – 27 May 2019

      Hi everyone,

      In the latest update, we shared that we’ll consider this suggestion for our longer term roadmap. Meanwhile, we've resolved JRASERVER-67811 which should help in cases when you’d like to assign a priority scheme to a large number of projects.

      By reviewing comments on this suggestion and context from the support cases, we have decided to provide an MVP solution, which will help you instantly with editing the default priority scheme and help us validate the longer term approach. Please note that this procedure is not part of the Jira’s intended functionality, and the information is provided as-is.

      In Jira Server 8.2, released last week, you can enable the labs feature of default priority scheme editing.

      Here are the steps to edit the default priority scheme:

      1. Enable the dark feature flag jira.priorities.per.project.edit.default.enabled by following these instructions.
      2. Go to 'View priority schemes' screen.
      3. Click the ‘Edit’ link next to the default priority scheme which will provide options available for non-default priority schemes.

      You can remove some of the priorities from the default scheme and keep them in the newly created schemes. If you have issues using the removed priorities, the priority will be marked as not available in the issue view and users will be able to change it manually.

      Please share your feedback on this solution so that we can make better decisions when solving the underlying problem. You can leave a comment here or reach out to me directly at kderenda(at)atlassian.com. 

      Jira Server 8.2 is available for download here. To read about other capabilities we added in Jira Software 8.2, have a look at our release notes.

      Katarzyna Derenda
      Product Manager, Jira Server

      Show
      Atlassian Update – 27 May 2019 Hi everyone, In the latest update, we shared that we’ll consider this suggestion for our longer term roadmap. Meanwhile, we've resolved JRASERVER-67811 which should help in cases when you’d like to assign a priority scheme to a large number of projects. By reviewing comments on this suggestion and context from the support cases, we have decided to provide an MVP solution, which will help you instantly with editing the default priority scheme and help us validate the longer term approach. Please note that this procedure is not part of the Jira’s intended functionality, and the information is provided as-is. In Jira Server 8.2, released last week, you can enable the labs feature of default priority scheme editing. Here are the steps to edit the default priority scheme: Enable the dark feature flag jira.priorities.per.project.edit.default.enabled by following these instructions . Go to 'View priority schemes' screen. Click the ‘Edit’ link next to the default priority scheme which will provide options available for non-default priority schemes. You can remove some of the priorities from the default scheme and keep them in the newly created schemes. If you have issues using the removed priorities, the priority will be marked as not available in the issue view and users will be able to change it manually. Please share your feedback on this solution so that we can make better decisions when solving the underlying problem. You can leave a comment here or reach out to me directly at kderenda(at)atlassian.com.  Jira Server 8.2 is available for download  here . To read about other capabilities we added in Jira Software 8.2, have a look at our release notes . Katarzyna Derenda Product Manager, Jira Server
    • 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.

      Problem Definition

      When new priority is created, it will automatically be added into the default priority scheme. This will be an issue when the default priority scheme has been used by many projects and users do not want the new priority scheme to be included in those projects.

      Suggested Solution

      It will be useful to have the ability to edit the default priority scheme and remove the newly created priority.

      Alternatively, removing the auto-adding of newly created priority scheme may be useful too.

      Workaround

      1. Create a new priority scheme
      2. Add all the priorities of the initial default priority scheme
      3. Associate all the affected projects with the scheme

      Need to actively associate new projects with this scheme

              Unassigned Unassigned
              imazuki Irfan Mazli Mazuki (Inactive)
              Votes:
              374 Vote for this issue
              Watchers:
              225 Start watching this issue

                Created:
                Updated: