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

Add auto-refresh functionality on Queues page

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • Queues
    • None

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

      Queues are now automatically updated. Animations indicating updates have been added in 2.5. See 2.5 Release Notes.

      The current Queues page requires a full page refresh to update the information displayed in it. There are a few use cases where auto-refresh would be a great feature to have.

      1. SLA values: Update the SLA values if displayed in any of the columns with a frequency that could either be setup to a default value or allow the user to choose how often this is required.

      2. New Issue created while in the Queue view: When a new ticket is created for the current JIRA SD project, update the Issue list by adding the new issue to the list. – Released in 2.4. Updated on May 11, 2015

      3. Issue has been updated by another person: Provide a message indicating that the Issue list has been updated. Similar to what JIRA Agile does.

          Form Name

            [JSDCLOUD-726] Add auto-refresh functionality on Queues page

            mh added a comment -

            Any  update? 

            mh added a comment - Any  update? 

            Christian Michaelis added a comment -

            +1

            Christian Michaelis added a comment - +1

            Matt Tittler added a comment -

            Also on JSD-404

            Matt Tittler added a comment - Also on JSD-404

            Matt Tittler added a comment -

            Please vote on JSD-433, already exists

            Matt Tittler added a comment - Please vote on JSD-433 , already exists

            IT added a comment -

            Frankly I'm amazed this only has 2 votes. How is a team supposed to track SLA's when they are static? Keep in mind not everyone works exclusively on queues. Most of our staff have 4 monitors and don't have time to keep updating tabs - too much mental bandwidth goes toward remembering to do so.

            Browser plugins to accomplish this are a mess - it requires us to install them on every staff's computer, properly configure it, ensure they don't mis/reconfigure it, etc. Plus it reloads the entire tab, which is more distracting (flickering window) and takes longer than "in-window" refreshing.

            If resource load is a concern, what about in-page refreshing like has been added to the bottom of the Issue Navigator? This could be done every 5-15 minutes and still be way ahead of requiring a manual refresh.

            Queues is a nice idea, but without auto-refresh (and a couple of other seemingly simple tweaks) it loses out to JIRA Agile workboards, the issue navigator and even dashboards.

            IT added a comment - Frankly I'm amazed this only has 2 votes. How is a team supposed to track SLA's when they are static? Keep in mind not everyone works exclusively on queues. Most of our staff have 4 monitors and don't have time to keep updating tabs - too much mental bandwidth goes toward remembering to do so. Browser plugins to accomplish this are a mess - it requires us to install them on every staff's computer, properly configure it, ensure they don't mis/reconfigure it, etc. Plus it reloads the entire tab, which is more distracting (flickering window) and takes longer than "in-window" refreshing. If resource load is a concern, what about in-page refreshing like has been added to the bottom of the Issue Navigator? This could be done every 5-15 minutes and still be way ahead of requiring a manual refresh. Queues is a nice idea, but without auto-refresh (and a couple of other seemingly simple tweaks) it loses out to JIRA Agile workboards, the issue navigator and even dashboards.

              llu lingbo (Inactive)
              6e107d394ed3 Rodolfo
              Votes:
              25 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: