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

Internet Explorer 8 (IE8) Performance when Using the Issue Navigator

      Problem Report

      When using the Internet Explorer 8.0.7600.16385 browser to navigate search results from Issue Navigator, a considerable slow performance can be observed.

      Steps to Reproduce:

      1. To replicate, go to the Issues tab and perform a search. Size of search results doesn't matter.
      2. Click on the Key of one of the issues.

        Problem 1: Takes 9 to 13 seconds for the view screen to finish loading so that functionality on the screen can be applied.

      3. Click on the Next issue button (top right of screen).

        Problem 2: Takes 10 to 15 seconds for the next issue to finish loading (so that the Next Issue button is enabled again).

      Workaround

      The usage of Internet Explorer 9.0.8112.16421 does not exhibit this problem.

            [JRASERVER-29497] Internet Explorer 8 (IE8) Performance when Using the Issue Navigator

            We've done some more testing on this and although we made some improvements in 6.0.6, I'm not happy with them so I'm reopening this issue.

            Eric Dalgliesh added a comment - We've done some more testing on this and although we made some improvements in 6.0.6, I'm not happy with them so I'm reopening this issue.

            Eric Dalgliesh added a comment - - edited

            There were some improvements through the life of 5.2.x, but not enough for us to consider this fixed. The earliest version of JIRA where this is fixed in 6.0.6.

            Regards,
            Eric

            EDIT: See my comment below. We made improvements in 6.0.6 but they turned out not to be as good as we expected so I've reopened this issue.

            Eric Dalgliesh added a comment - - edited There were some improvements through the life of 5.2.x, but not enough for us to consider this fixed. The earliest version of JIRA where this is fixed in 6.0.6. Regards, Eric EDIT: See my comment below. We made improvements in 6.0.6 but they turned out not to be as good as we expected so I've reopened this issue.

            Hello,

            is there a fix for JIRA 5.2?

            Regards,
            Tim

            Tim Eddelbüttel added a comment - Hello, is there a fix for JIRA 5.2? Regards, Tim

            Hi,

            This issue looks like it is related to JRA-33751 which is causing us major problems and is stopping us being able to upgrade to JIRA 6.

            Thanks,

            Alistaur

            Alistair Clare added a comment - Hi, This issue looks like it is related to JRA-33751 which is causing us major problems and is stopping us being able to upgrade to JIRA 6. Thanks, Alistaur

            ChrisA added a comment -

            Hi chris.smith@tekcomms.com, my apologies for that, I've asked our Support team to look into it further for you. Whilst we might not be able to solve performance completely we would like to at least understand what options we do have to improve it.

            Regards,

            Chris Le Petit
            Service Enablement

            ChrisA added a comment - Hi chris.smith@tekcomms.com , my apologies for that, I've asked our Support team to look into it further for you. Whilst we might not be able to solve performance completely we would like to at least understand what options we do have to improve it. Regards, Chris Le Petit Service Enablement

            I have. Support has logged it as a bug, https://support.atlassian.com/browse/JSP-166269.

            Chris Smith added a comment - I have. Support has logged it as a bug, https://support.atlassian.com/browse/JSP-166269 .

            Hi chris.smith@tekcomms.com, that doesn't sound right. Could you contact support to help figure out what's going on?

            Regards,
            Eric

            Eric Dalgliesh added a comment - Hi chris.smith@tekcomms.com , that doesn't sound right. Could you contact support to help figure out what's going on? Regards, Eric

            Question then. If I am running the Issue Navigator in "Advanced" mode I am not presented with options to select from, just a JQL text box. So are these items still loaded during when the "Advanced" option becomes enabled? It would seem the process by which the JQL box performs the predictive text slows down text additions, as well as the predictive text does not suggest an option in IE8. We are barely in Production with limited custom fields (maybe 15), limited projects (maybe 20), etc.. and if it works in Chrome and Firefox (I guess), then why is Atlassian blaming the amount of setup data.

            Chris Smith added a comment - Question then. If I am running the Issue Navigator in "Advanced" mode I am not presented with options to select from, just a JQL text box. So are these items still loaded during when the "Advanced" option becomes enabled? It would seem the process by which the JQL box performs the predictive text slows down text additions, as well as the predictive text does not suggest an option in IE8. We are barely in Production with limited custom fields (maybe 15), limited projects (maybe 20), etc.. and if it works in Chrome and Firefox (I guess), then why is Atlassian blaming the amount of setup data.

            Typically this occurs when there are a lot of options in one of the drop downs, so having lots of components, versions, custom fields and/or projects can lead to this.

            Eric Dalgliesh added a comment - Typically this occurs when there are a lot of options in one of the drop downs, so having lots of components, versions, custom fields and/or projects can lead to this.

            FlorinM added a comment -

            Is there any info you can share about the "particular shapes" of data? Maybe it's possible for some to work around these.

            FlorinM added a comment - Is there any info you can share about the "particular shapes" of data? Maybe it's possible for some to work around these.

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              jalex Justin Alex [Atlassian] (Inactive)
              Affected customers:
              15 This affects my team
              Watchers:
              34 Start watching this issue

                Created:
                Updated:
                Resolved: