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

Make Queue Count Search individually based on the current queue

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Queues
    • 2
    • 12
    • 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.

      Problem Definition

      Queue Count Search is being performed to all Queues throughout the Project, regardless of which Queue is currently worked on. This leads to noticeable loading time when Queues are using complex JQL.

      Suggested Solution

      Make the Queue Count Search only performed on the current Queue rather than the whole Queues in the project. Perhaps the Queue Count Search for the entire project can only be performed after a set interval or certain specific actions.

      Workaround

      It is possible to disable the Queue Count Search on Project Level or Globally via REST API. However, this will disable the Queue Counter.
      It is suggested to test out the REST API on a testing instance first.
      Global (Entire JIRA instance):

      PUT <contextpath>/rest/servicedeskapi/admin/queues/include-count - true/false body - 200 response (default true)

      Per project:

      PUT <contextpath>/rest/servicedeskapi/admin/queues/<projectkey>/include-count - true/false body - 200 response (default true)

          Form Name

            [JSDSERVER-6424] Make Queue Count Search individually based on the current queue

            Charlie Marriott added a comment -
            Atlassian Update – 6 July 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Charlie

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 6 July 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Charlie Jira Service Management, Server & Data Center

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

                Created:
                Updated: