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

Allow better grouping when there are many portals

XMLWordPrintable

    • 5
    • 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.
      Cheers,
      The JIRA Service Desk team

          Form Name

            [JSDSERVER-777] Allow better grouping when there are many portals

            Pedram Mireftekhari added a comment -

            It would also be nice for when there is only one project or the customer has access to only one project, the landing first page on the portal for the customer to be the request type grouping, not the project. This is already in place in Cloud deployment why not on-prem? I want to see only the request-type groups, not the project and then click on the project name and see the request-type groups.

            Pedram Mireftekhari added a comment - It would also be nice for when there is only one project or the customer has access to only one project, the landing first page on the portal for the customer to be the request type grouping, not the project. This is already in place in Cloud deployment why not on-prem? I want to see only the request-type groups, not the project and then click on the project name and see the request-type groups.

            Katarzyna Pawlak [Deviniti] added a comment -

            Hi, 

            You can add categories to your Help Center using our app Theme Extension for Jira Service Desk.

            Regards,

            Kate

            Katarzyna Pawlak [Deviniti] added a comment - Hi,  You can add categories to your Help Center using our app Theme Extension for Jira Service Desk . Regards, Kate

            Jeremy Largman added a comment -

            I've updated the title of this ticket - I thought the specific implementation of a multi-level select field wasn't needed; we could also implement this using groupings of portals. Given that we now have a portal of portals, this could also be configured using grouping of portals.

            Jeremy Largman added a comment - I've updated the title of this ticket - I thought the specific implementation of a multi-level select field wasn't needed; we could also implement this using groupings of portals. Given that we now have a portal of portals, this could also be configured using grouping of portals.

              Unassigned Unassigned
              mnassette MJ (Inactive)
              Votes:
              22 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated: