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

Epic link dropdown slow in large instances

XMLWordPrintable

    • 7
    • Hide
      Atlassian Update – 24 Jan 2022

      Hi everyone,

      I am happy to announce that this issue should be resolved in 8.22.0.

      Thank you,
      Szymon Korytnicki,
      Jira Data Center Developer

      Show
      Atlassian Update – 24 Jan 2022 Hi everyone, I am happy to announce that this issue should be resolved in 8.22.0. Thank you, Szymon Korytnicki, Jira Data Center Developer
    • 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.

      Summary

      Despite the fix in JSWSERVER-20452, it takes more than 20s to load the epic dropdown in large instances (300k+ epics)

      Steps to Reproduce

      1. Create 300k epics in an instance.
      2. Open the epic link on an issue.

      Expected Results

      The epics should load only partially and fast, the same way we do with user list in the assignee field.

      Actual Results

      We load all epics from the index, this can take more than 20s.

      Workaround

      Archive unused or closed epics.

          Form Name

            [JSWSERVER-21026] Epic link dropdown slow in large instances

            Szymon Korytnicki (Inactive) added a comment -

            Hi all, the fix has been backported to 8.13.20 (next release of 8.13)

            Szymon Korytnicki (Inactive) added a comment - Hi all, the fix has been backported to 8.13.20 (next release of 8.13)

            Szymon Korytnicki (Inactive) added a comment -

            The update will be released in next LTS release, 8.20.7

            Szymon Korytnicki (Inactive) added a comment - The update will be released in next LTS release, 8.20.7

            Szymon Korytnicki (Inactive) added a comment -

            110e6bdd726b, I can't give you specific date at the moment, but it's the next version to be released and there's first EAP available already. This EAP does not contain updates to Epic picker though. Next EAP will do and it should be available soon.

            https://confluence.atlassian.com/jiracore/preparing-for-jira-8-22-1108676240.html

            Adding this fix to LTS was my first idea. However, we ended up on rewriting epic picker logic from scratch and minor changes in behaviour can be expected; results returned by the dropdown should be similar but not the same. We're affecting REST endpoint and JQL autocomplete too. This is why we picked the conservative option to ship to 8.22. If we don't encounter major problems, we will backport this fix to LTS.

            I will keep you in the loop.

            Szymon Korytnicki (Inactive) added a comment - 110e6bdd726b , I can't give you specific date at the moment, but it's the next version to be released and there's first EAP available already. This EAP does not contain updates to Epic picker though. Next EAP will do and it should be available soon. https://confluence.atlassian.com/jiracore/preparing-for-jira-8-22-1108676240.html Adding this fix to LTS was my first idea. However, we ended up on rewriting epic picker logic from scratch and minor changes in behaviour can be expected; results returned by the dropdown should be similar but not the same. We're affecting REST endpoint and JQL autocomplete too. This is why we picked the conservative option to ship to 8.22. If we don't encounter major problems, we will backport this fix to LTS. I will keep you in the loop.

            Brian Bobryk added a comment -

            As this issue impacts large installations running Jira Data Center, will this fix also be made available on prior LTS release versions such as 8.20 and 8.13 ? We are currently running 8.13.9 in production and moving to 8.20. Our instance has 4 million issues with over 94K epics currently in use and the link performance is a major issue for these versions of Jira.

            Brian Bobryk added a comment - As this issue impacts large installations running Jira Data Center, will this fix also be made available on prior LTS release versions such as 8.20 and 8.13 ? We are currently running 8.13.9 in production and moving to 8.20. Our instance has 4 million issues with over 94K epics currently in use and the link performance is a major issue for these versions of Jira.

            RAP472 added a comment -

            Thank you for the update @szymon. Can you tell us when version 8.22.0 is expected to be released?

            RAP472 added a comment - Thank you for the update @szymon. Can you tell us when version 8.22.0 is expected to be released?

            RAP472 added a comment -

            I'd like to echo @rachel purpel's comment. While there are workarounds, I have users who are more familiar with adding Epics through the dropdown, so they use this lag as a reason to not enter the corresponding Epic, which leads to a lot of cleanup efforts. This in turn leads to inaccurate data in our reporting.

            RAP472 added a comment - I'd like to echo @rachel purpel's comment. While there are workarounds, I have users who are more familiar with adding Epics through the dropdown, so they use this lag as a reason to not enter the corresponding Epic, which leads to a lot of cleanup efforts. This in turn leads to inaccurate data in our reporting.

            Rachel Purpel added a comment -

            The poor responsiveness on populating the Epic Link drop-down causes the "Jira is slow" perception at my organization. 

            Rachel Purpel added a comment - The poor responsiveness on populating the Epic Link drop-down causes the "Jira is slow" perception at my organization. 

              292ec441c8da Szymon Korytnicki (Inactive)
              adridi Arbi Dridi
              Votes:
              11 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: