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

Versions view in Project settings can timeout on large instance

XMLWordPrintable

    • 7.02
    • 51
    • Severity 2 - Major
    • 269
    • Hide
      Atlassian Update – 9 April 2020

      Hi everyone,

      We've improved the experience for versions page in project settings in Jira Server and Data Center Enterprise release versions 7.13.x and 8.5.5. The improvement will also be available in the upcoming Jira 8.9 release.

      Thanks for your feedback on this issue and contacting our support team with specific use cases to work on.
      Kind regards,
      Mateusz Ostaszewski

      Jira Server and Data Center Team

      Show
      Atlassian Update – 9 April 2020 Hi everyone, We've improved the experience for versions page in project settings in Jira Server and Data Center Enterprise release versions 7.13.x and 8.5.5. The improvement will also be available in the upcoming Jira 8.9 release. Thanks for your feedback on this issue and contacting our support team with specific use cases to work on. Kind regards, Mateusz Ostaszewski Jira Server and Data Center Team

      Summary

      Versions view in project settings is using a single query to Jira's internal REST (GET /rest/projects/1.0/project/<KEY>/release/allversions) to gather all of the versions data. The query can be slow due to accessing index multiple times for each version.

      The query can timeout in Jira's frontend resulting in versions list not being shown up.

      Environment

      • Large Jira instance
        • with large Lucene (a large number of issues 1M+)
        • with project containing many issues with many versions (2000+)

      Steps to Reproduce

      1. Access <jira>/plugins/servlet/project-config/<ProjectKey>/administer-versions
        (replace <jira> with Jira's base URL and <ProjectKey> with large project's ID)

      Expected Results

      Versions list loads.

      Actual Results

      Versions list request times out with the message:

      The call to the JIRA server did not complete within the timeout period.
      We are unsure of the result of this operation.
      

      Notes

      Slow loading of ..release/allversions is caused by 2 factors

      • a large number of versions in the return list (in the project)
      • a time required to calculate data for each version (4 Lucene calls are executed)

      Workaround

      • There is no workaround so far.
      • You may want to use old version page with similar functionality: <jira>/plugins/servlet/project-config/<PROJ>/versions

      This is how the new page looks like:

      And how the old page looks like:

              Unassigned Unassigned
              pczuj Przemyslaw Czuj
              Votes:
              72 Vote for this issue
              Watchers:
              92 Start watching this issue

                Created:
                Updated:
                Resolved: