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

Allow Service Desk queues to be grouped

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Queues
    • 32
    • 6
    • 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 Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.

      Summary

      In JIRA ServiceDesk, you are able to add queues in order to organise work. This is good for categorising tasks based on various use-cases, such as Geographical Distribution of Employees, or to highlight issues that need the most amount of attention.

      Creating many queues causes a long list to form, which is may be difficult to navigate under some circumstances.

      Steps to Reproduce

      In a JIRA Service Desk:

      1. Make many queues as per: Make queues for your service desk teams
      2. Observe that as the list gets longer, it is harder to navigate.

      Expected Results

      A method to collapse, or arrange Service Desk queues in a logical fashion.

      Actual Results

      No method to arrange queues into sub-categories exists.

      Workaround

      Some users have discovered by:

      1. Clicking the Queues Tab
      2. Create a New Queue
      3. Using Unicode characters such as: ↳ U+2183 in the name of the queue, meets their requirements.

      Original Submitted Request:

      Like anything else, as soon as you have more than a handful of queues, having some method to group queues become important.

      This is what we have right now in our SD implementation, but what we really want is to be able to group queues ( and probably reports too ). See attached.

      Our base scenario is that we are setting up a single Service Queue so we can have a single Customer Portal entry point, but we have multiple teams ( Systems Support, Software Support, Data, ... ) as service agents, and need to setup queues for them.

      We also have multiple locations, and again want to offer a single entry point for our users, but share the backend so support teams can cover for remote locations ( which may or may not have local teams ). This could also be resolved if the customer portal was separated from the agent portal so they could be mixed and matched based on usage patterns ( one to one, many to one, one to many, ... )

      Attachments

        1. flat_queues.png
          flat_queues.png
          30 kB
        2. grouped_queues.png
          grouped_queues.png
          38 kB
        3. Screen Shot 2017-03-20 at 9.39.26 PM.png
          Screen Shot 2017-03-20 at 9.39.26 PM.png
          2 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              e887a69c641b Olivier Ozoux
              Votes:
              205 Vote for this issue
              Watchers:
              102 Start watching this issue

              Dates

                Created:
                Updated:

                Backbone Issue Sync