Impossible to add JIRA pie chart macro when the primary applink of JIRA is not reachable or the Oauth token expired

XMLWordPrintable

    • 2
    • Severity 3 - Minor

      Issue Summary

      When the primary applink of JIRA is not responsive, it is impossible to add a JIRA pie chart macro on the page. The macro popup window will disappear instantly with no error message on the UR, but with the following JS error in the console:

      batch.js?locale=en-US:326 Uncaught SyntaxError: Unexpected token < in JSON at position 0
          at JSON.parse (<anonymous>)
          at Object.error (batch.js?build-number=7201&confluence.table.resizable=true&confluence.view.edit.transition=true&is-server-instance=true&locale=en-US:4211)
          at k (batch.js?locale=en-US:195)
          at Object.fireWith [as rejectWith] (batch.js?locale=en-US:196)
          at c (batch.js?locale=en-US:321)
          at b (batch.js?locale=en-US:333)
          at Object.send (batch.js?locale=en-US:333)
          at Function.ajax (batch.js?locale=en-US:326)
          at Object.makeRequest (batch.js?build-number=7201&confluence.table.resizable=true&confluence.view.edit.transition=true&is-server-instance=true&locale=en-US:3883)
          at Object.d [as populateStatType] (batch.js?build-number=7201&confluence.table.resizable=true&confluence.view.edit.transition=true&is-server-instance=true&locale=en-US:4211)
      error @ batch.js?build-number=7201&confluence.table.resizable=true&confluence.view.edit.transition=true&is-server-instance=true&locale=en-US:4211
      k @ batch.js?locale=en-US:195
      

      Steps to Reproduce

      1. Create 2 JIRA application links on Confluence.
      2. Stop the JIRA instance of the primary applink
      3. Open a page and try to add a pie chart macro

      Expected Results

      The macro popup window should show with the list of available JIRA server.

      Actual Results

      The popup window closes immediately without any error message as well as access the JIRA pie chart via the JIRA issue macro.

      Notes

      Apparently, if the user has not yet created the JIRA Oauth Token on the primary JIRA instance, we will encounter the same issue.

      Workaround

      • Remove the unresponsive JIRA instance from the primary applink.
      • In case the JIRA instance is reachable, ask the end-user to create JIRA issue macro with the primary JIRA instance to create the Oauth Token before adding the pie chart macro.

              Assignee:
              George Lipatov
              Reporter:
              Yilin (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: