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

Allow better grouping when there are many portals



    • 4
    • 5
    • 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.


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

      Having to manually choose a project when raising a service desk request, issue can easily end up in wrong projects or with wrong issue types.
      This particularly happens in environments where high numbers of projects are using service desk and/or the reporters are external users or users who do not frequently use that instance of JIRA.
      When using a multi-level select or a (sub-)component field in the create issue screen, you can automate which project the request ends up in, and which issue-type it receives.

      Update as of 21 May 2015

      Hi everyone,

      Just to give you a quick update: we've been monitoring this suggestion and understand that this is not the ideal situation. This is not on our short-term roadmap and we'll come back to it later.
      The JIRA Service Desk team


        Issue Links



              Unassigned Unassigned
              mnassette MJ (Inactive)
              21 Vote for this issue
              16 Start watching this issue



                Backbone Issue Sync