Issue Summary

      When there more than ~60 issues in backlog, user face slowness while creating issue from the backlog.

      Environment

      • Jira 8.X
      • Google Chrome 75.X

      Steps to Reproduce

      1. Create more than 60 issues in the backlog. We can use Jira Data Generator to generate the issues.
      2. Ensure that the 60 issues are displayed in a backlog of a board.
      3. Access the board where the issues are displayed, click on "Create issue" and enter the summary of the issue.

      Expected Results

      • Use do not see any slowness while entering the issue summary.

      Actual Results

      • User see noticeable slowness while entering the issue summary.

      Workaround

      • Use a browser other than Google Chrome.

      Note

      While there's a noticeable delay in adding Summary, there's no problem creating issue from backlog with Chrome.

          Form Name

            [JSWSERVER-20130] Slow issue creation with Google Chrome in backlog

            Fixed by Chrome update to 76.x

            Dmytro Borshchov added a comment - Fixed by Chrome update to 76.x

            Hi Folks!

            This issue should be resolved by the release of Chrome 76 (as per discussions over at https://jira.atlassian.com/browse/JRASERVER-69568). Please let us know if you're continuing to see slowness in Chrome in Jira 8 boards

            We'll leave both tickets open a little longer to verify that the browser update fixes the problem and collect more information - and if we haven't heard anything in a week, we'll mark them as resolved.

            Cheers,
            Dave
            Senior Support Engineer (Sydney)

            Dave Norton added a comment - Hi Folks! This issue should be resolved by the release of Chrome 76 (as per discussions over at https://jira.atlassian.com/browse/JRASERVER-69568 ). Please let us know if you're continuing to see slowness in Chrome in Jira 8 boards We'll leave both tickets open a little longer to verify that the browser update fixes the problem and collect more information - and if we haven't heard anything in a week, we'll mark them as resolved. Cheers, Dave Senior Support Engineer (Sydney)

              Unassigned Unassigned
              vshanmugam Vicknesh Shanmugam (Inactive)
              Affected customers:
              6 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: