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

Clicking Link from the More dialog in an issue results in a loading spinner that never completes

XMLWordPrintable

    • 7.03
    • 25
    • Severity 2 - Major
    • 4
    • Hide
      Atlassian Update – 7th March 2018

      Hi everyone,

      I am happy to announce that we have addressed the issue starting with the 7.6.4 Server version. Please have a look at the Fix Version/s field for the list of subsequent versions that will include the fix as well.

      This flaw turned out to be a manifestation of a wider, cross-product problem. We have improved loading of the dialog in terms of reliability. At the same time, for that any such occurrences rely heavily on an actual Jira's configuration (e.g. installed plugins) and we were not able to test all the possible setups, an error dialog containing suggested workaround will be presented to a user shall the Link Issue dialog fail to render ever again. The workaround is
      https://confluence.atlassian.com/display/JIRAKB/JIRA+elements+fail+to+render+with+HTTP+400+error  it proved to be efficient every time it was applied.
      We will be also monitoring performance of the Link Issue dialog in order to assess whether further action is needed.

      Cheers,
      Pawel Drygas
      Developer, Jira Server

      Show
      Atlassian Update – 7th March 2018 Hi everyone, I am happy to announce that we have addressed the issue starting with the 7.6.4 Server version. Please have a look at the Fix Version/s field for the list of subsequent versions that will include the fix as well. This flaw turned out to be a manifestation of a wider, cross-product problem. We have improved loading of the dialog in terms of reliability. At the same time, for that any such occurrences rely heavily on an actual Jira's configuration (e.g. installed plugins) and we were not able to test all the possible setups, an error dialog containing suggested workaround will be presented to a user shall the Link Issue dialog fail to render ever again. The workaround is https://confluence.atlassian.com/display/JIRAKB/JIRA+elements+fail+to+render+with+HTTP+400+error   it proved to be efficient every time it was applied. We will be also monitoring performance of the Link Issue dialog in order to assess whether further action is needed. Cheers, Pawel Drygas Developer, Jira Server

      Summary

      In order to link either another JIRA issue or a Confluence page to an issue, an end-user attempts to open the "Link" dialog, either by choosing "More" > "Link", or by using the dot-dialog and typing "Link".

      Expected results

      The Link issue dialog appears, allowing the user to link either a JIRA issue or Confluence page.

      Actual results

      The page is dimmed and a spinner appears over the page. The spinner never disappears.

      Additional observations

      When checking the HTTP requests and responses for the page, one (or more) batch.js files have an error response of: HTTP 400 "Bad Request".

            [JRASERVER-64982] Clicking Link from the More dialog in an issue results in a loading spinner that never completes

            bewalser added a comment - - edited

            After contacting Support this fixed our issue with "Link feature" and loading spinner: 

            https://confluence.atlassian.com/jirakb/jira-elements-fail-to-render-with-http-400-error-860033769.html

             

            bewalser added a comment - - edited After contacting Support this fixed our issue with "Link feature" and loading spinner:  https://confluence.atlassian.com/jirakb/jira-elements-fail-to-render-with-http-400-error-860033769.html  

            Daz added a comment -

            From what I recall of the fragmented conversations in Support, this issue occurs on JIRA instances hosted via IIS.

            Before JIRA 7.3.2, the batch.js files JIRA served had paths where each "directory" piece – i.e., the bit between the forward-slash ("/") characters – was less than 260 characters long.

            In JIRA 7.3.2 and later, some batch.js files have directory pieces that are 260 or more characters in length.

            It's a known issue that IIS responds to these requests with an HTTP 400 "Bad Request". JIRA does not get involved in this process.

            If the root cause is IIS + parts of URL length, we will need to do two things to fix the problem:

            1. Patch the WebResourceManager (WRM) to split the directory pieces if they would exceed 255 characters in length.
            2. Investigate and attempt to coerce JIRA's URLs to be shorter.
              1. We would need to adjust the various contexts and web-resources that get required on the pages, as the final URL is constructed via the WRM and is largely out of our control, except for the length of the names of the contexts + web-resources that are being required.

             

            Daz added a comment - From what I recall of the fragmented conversations in Support, this issue occurs on JIRA instances hosted via IIS. Before JIRA 7.3.2, the batch.js files JIRA served had paths where each "directory" piece – i.e., the bit between the forward-slash ("/") characters – was less than 260 characters long. In JIRA 7.3.2 and later, some batch.js files have directory pieces that are 260 or more characters in length. It's a known issue that IIS responds to these requests with an HTTP 400 "Bad Request". JIRA does not get involved in this process. If the root cause is IIS + parts of URL length, we will need to do two things to fix the problem: Patch the WebResourceManager (WRM) to split the directory pieces if they would exceed 255 characters in length. Investigate and attempt to coerce JIRA's URLs to be shorter. We would need to adjust the various contexts and web-resources that get required on the pages, as the final URL is constructed via the WRM and is largely out of our control, except for the length of the names of the contexts + web-resources that are being required.  

              pdrygas Pawel Drygas (Inactive)
              cdarroch Daz
              Affected customers:
              11 This affects my team
              Watchers:
              26 Start watching this issue

                Created:
                Updated:
                Resolved: