Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-1374

Priorities per Service Desk project

    XMLWordPrintable

Details

    • We collect Jira Service Desk 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.

    Description

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

      Atlassian update as of 15th January 2018

      Hi everyone,

      Great news - The ability to set Priority schemes in Jira Service Desk project(s) is now available with Jira Service Desk version 3.10. To find out more about this feature, check out our release notes here.

      On behalf of the JSD team, I want to thank all of you for patience.

      Cheers,
      Jira Service Desk Team

      Due to the missing functionality of having "Priority per project" in JIRA (JRA-3821), the JIRA default priority is useless when you have more than the default priorites. Which is a need if you have a big JIRA instance and many projects.

      I think the main solution must be made in JIRA core rather than in Service Desk but respect the workaround from the linked issue will be a quick fix for the customer portal.

      And maybe the SD Team can give the linked issue some higher rank in the Backlog.

      Attachments

        Issue Links

          is duplicated by

          Suggestion - JSDSERVER-3400 Allow for Service Desk to use it's own priority schema while not impacting Jira's Priorities

          • Closed
          relates to

          Suggestion - JRASERVER-3821 Priorities per Project and Resolutions per Issue Type

          • Closed

          Suggestion - JSDCLOUD-1374 Priorities per Service Desk project

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              4e81381d415c Tim Eddelbüttel
              Votes:
              12 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync