Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9920

Improve the way the Backlog is loaded for better performance and/or rendering of a large number of items

XMLWordPrintable

    • 21
    • 37
    • Hide
      Atlassian Update – 21 December 2018

      Dear Jira users,

      We’re glad to announce that this issue will be addressed in our upcoming 8.0 release.

      You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588

      Looking forward to your feedback!

      Kind regards,
      Syed Masood
      Product Manager, Jira Server and Data Center

      Show
      Atlassian Update – 21 December 2018 Dear Jira users, We’re glad to announce that this issue will be addressed in our upcoming 8.0 release. You can find more details about our 8.0 beta release here — https://community.developer.atlassian.com/t/beta-for-jira-8-0-is-up-for-grabs/25588 Looking forward to your feedback! Kind regards, Syed Masood Product Manager, Jira Server and Data Center
    • We collect Jira 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 Software Server. Using JIRA Software Cloud? See the corresponding suggestion.

      Problem Definition

      When there are many issues on the board, the load time is pretty bad.

      Edit: incorporating performance for epics and versions

      Suggested Solution

      We could 'paginate' the results to improve the experience for example. Ie. Once a user scrolls down, we can load the other issues which are ranked below the bottom of the screen.

      Notes
      • Agile pefromance logging - you can enable DEBUG for com.atlassian.greenhopper.performance which will give you breakdown for slow request, example of output: 
        /// Full line: 2018-06-13 21:59:20,824 ... /rest/greenhopper/1.0/xboard/plan/backlog/data.json [com.atlassian.greenhopper.performance

2018-06-13 21:59:20,824 ... /data.json [com.atlassian.greenhopper.performance] SearchProvider.search  8ms
2018-06-13 21:59:20,841 ... /data.json [com.atlassian.greenhopper.performance] SearchProvider.searchAndSort  13ms
2018-06-13 21:59:20,841 ... /data.json [com.atlassian.greenhopper.performance] collectIssues (search and callback)   15ms
2018-06-13 21:59:20,841 ... /data.json [com.atlassian.greenhopper.performance] collectIssues (callback only) 8ms
2018-06-13 21:59:20,844 ... /data.json [com.atlassian.greenhopper.performance] SearchProvider.search  2ms
2018-06-13 21:59:20,850 ... /data.json [com.atlassian.greenhopper.performance] SearchProvider.searchAndSort  2ms
2018-06-13 21:59:20,850 ... /data.json [com.atlassian.greenhopper.performance] collectIssues (search and callback)   3ms
2018-06-13 21:59:20,850 ... /data.json [com.atlassian.greenhopper.performance] collectIssues (callback only) 1ms
2018-06-13 21:59:20,852 ... /data.json [com.atlassian.greenhopper.performance] SearchProvider.search  1ms
2018-06-13 21:59:20,862 ... /data.json [com.atlassian.greenhopper.performance] SearchProvider.search  1ms
        • note: collectIssues (callback only) 8ms

              tjoy Tilwin Joy
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              86 Vote for this issue
              Watchers:
              73 Start watching this issue

                Created:
                Updated:
                Resolved: