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 Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-90868

Epic link drop-down poor performance with large amounts of epic links

      Update Feb 16th, 2024

      Hi everyone,

      This bug is about the performance of the Epic Link field.

      This field has now been disabled on the Jira issue view and replaced by the Parent field ([full announcement here|https://community.atlassian.com/t5/Jira-Software-articles/Introducing-the-new-Parent-field-in-company-managed-projects/ba-p/2377758 ]) that is already rolled out to everyone.

      With that, we are closing this bug. 

       

      Regards,

      Irene Ongkowidjaja

      Summary

      Depending on the number of epic links you have on your project, you may find out that the drop-down menu search is not actually performing well.

      Steps to Reproduce

      1. Having an instance with more than 3K epic links
      2. Create or edit an issue, try to fetch the epic links drop-down list

      Expected Results

      • The list will be rendered in at least 5 seconds

      Actual Results

      • Depending on the sheer number of epic links and their status it can take up to 20 seconds to load the whole list.

      Workaround

      1. Change status of epic links unused to DONE
      2. Unmark the option "Show done epics" if it's marked.

            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 Platform Cloud'
            1. Jira Platform Cloud
            2. JRACLOUD-90868

            Epic link drop-down poor performance with large amounts of epic links

                Update Feb 16th, 2024

                Hi everyone,

                This bug is about the performance of the Epic Link field.

                This field has now been disabled on the Jira issue view and replaced by the Parent field ([full announcement here|https://community.atlassian.com/t5/Jira-Software-articles/Introducing-the-new-Parent-field-in-company-managed-projects/ba-p/2377758 ]) that is already rolled out to everyone.

                With that, we are closing this bug. 

                 

                Regards,

                Irene Ongkowidjaja

                Summary

                Depending on the number of epic links you have on your project, you may find out that the drop-down menu search is not actually performing well.

                Steps to Reproduce

                1. Having an instance with more than 3K epic links
                2. Create or edit an issue, try to fetch the epic links drop-down list

                Expected Results

                • The list will be rendered in at least 5 seconds

                Actual Results

                • Depending on the sheer number of epic links and their status it can take up to 20 seconds to load the whole list.

                Workaround

                1. Change status of epic links unused to DONE
                2. Unmark the option "Show done epics" if it's marked.

                        Unassigned Unassigned
                        dbrito Daniel Brito [Atlassian]
                        Votes:
                        62 Vote for this issue
                        Watchers:
                        58 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            dbrito Daniel Brito [Atlassian]
                            Affected customers:
                            62 This affects my team
                            Watchers:
                            58 Start watching this issue

                              Created:
                              Updated:
                              Resolved: