Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-4897

Loading issue count is slow when there are many queues in single project



    • Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 35
    • 12
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.


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

      Problem Definition

      A customer saw queues taking up to 20s to load (with 35 queues in a single projects). This was because the count issues method uses jql search using LuceneSearchProvider in JIRA core to count issues for any queue. Issues for all queues are counted at page load, queue update, add issue and the polling on the queues page, to show the issue count lozenge on the left hand panel.

      Suggested Solution

      1. store the project specific setting using the GlobalPropertyDao
      2. currently issue count is done by JQL search in JIRA core
      3. QueueServiceImpl accepts a bool to shouldCount for queues
      4. CustomQueuesItemProvider:getqueues provides a true value for shouldCount
      5. QueueAssemblerImpl:getQueues provides a shouldCount value that is passed through API call and that is false by default.


      1. Reduce the amount of queues per project
      2. Simplify the JQL search in each queues (avoid using SLA check when possible)


        Issue Links



              Unassigned Unassigned
              vkharisma vkharisma (Inactive)
              10 Vote for this issue
              16 Start watching this issue