Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-68497

SQL for checking usages of version in custom fields is slow even if no version picker custom fields exist

XMLWordPrintable

    • 7
    • Severity 2 - Major
    • 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

      Summary

      When deleting a version, Jira checks if the version is used in custom fields.
      This is done in methods versionService.getCustomFieldIssuesCount and versionService.getCustomFieldsUsing.

      The check is very slow on big instances, even if the instance contains no custom fields that are version pickers.

      Expected results

      If instance contains no custom version pickers, the queries should execute almost immediately.

      Notes

      For a bigger context, see https://jira.atlassian.com/browse/JRASERVER-67198
       

              drauf Daniel Rauf
              drauf Daniel Rauf
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: