We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
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.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            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.

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

                          Created:
                          Updated:
                          Resolved:

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

                              Created:
                              Updated:
                              Resolved: