Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10021

Issue detail fails to render with a JS error when viewing an issue which has issue links

XMLWordPrintable

      Here is the step to reproduce the issue:

      1. Install the JIRA agile plugin on JIRA 5.2.x
      2. Create a new project with a scrum board
      3. Create an issue link to link between issue1 and issue2.
      4. Display the issue detail on the plan view and it failed for both issue1 and issue2 with the following error: 
        An error occurredHide…
Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues.
Details
Exception: Uncaught TypeError: Cannot read property 'statusCategory' of undefined
Resource: http://mymac:6521/s/en_US10h4q1-418945332/854/4/f87f04f2effa3135432ccc7a7836806a/_/download/contextbatch/js/gh-rapid/batch.js
Line: 721
Environment
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1599.101 Safari/537.36

      It seems that is an compatibility issue with JIRA 5.2.x as it works correctly on JIRA 6.1.x

      Workaround

      Either of the following can workaround the problem:

      • Upgrade JIRA as per Upgrading JIRA to the latest version.
      • Edit the board configuration in Board > Configure > Issue Detail View and remove the "Linked Issues" column from Links as per the attached screenshot. After the bug is fixed, remember to add these back. As a side effect no issue links will be displayed for the issue view.

        1. Configure Board.png
          Configure Board.png
          9 kB

            [JSWSERVER-10021] Issue detail fails to render with a JS error when viewing an issue which has issue links

            Roger Mortimer added a comment -

            +1 What Peter Jaffe says - no problem after the upgrade. Thanks.

            Roger Mortimer added a comment - +1 What Peter Jaffe says - no problem after the upgrade. Thanks.

            Michael Tokar added a comment -

            blaisbr please raise a support request with our Support Team as this looks like it could be a different issue.

            Michael Tokar added a comment - blaisbr please raise a support request with our Support Team as this looks like it could be a different issue.

            Pete Jaffe added a comment - - edited

            For what it's worth, I had removed "Linked Issues" from my Details View of my Agile boards because I was hitting the original failure described in this issue. I accepted the upgrade to JIRA Agile 6.3.4.3 last Friday, added "Linked Issues" back into my Details View, and things are working great for me. Thanks for the fix.

            I personally haven't see the "TypeError: M is undefined" exception before that DIGIT CITnet Support is reporting.

            Pete Jaffe added a comment - - edited For what it's worth, I had removed "Linked Issues" from my Details View of my Agile boards because I was hitting the original failure described in this issue. I accepted the upgrade to JIRA Agile 6.3.4.3 last Friday, added "Linked Issues" back into my Details View, and things are working great for me. Thanks for the fix. I personally haven't see the "TypeError: M is undefined" exception before that DIGIT CITnet Support is reporting.

            DIGIT CITnet added a comment -

            I did the upgrade to the latest version and now I have another error: 'M' undefined

            DIGIT CITnet added a comment - I did the upgrade to the latest version and now I have another error: 'M' undefined

            Michael Tokar added a comment -

            Dawn, if you have a valid license you should be able to receive updates to JIRA Agile. If this is not the case please contact our Support Team.

            Michael Tokar added a comment - Dawn, if you have a valid license you should be able to receive updates to JIRA Agile. If this is not the case please contact our Support Team .

            Dawn Fama added a comment -

            Hello John,

            The link to the Agile pluggin you reference here: https://marketplace.atlassian.com/plugins/com.pyxis.greenhopper.jira is not a free update like the initial update.

            Dawn Fama added a comment - Hello John, The link to the Agile pluggin you reference here: https://marketplace.atlassian.com/plugins/com.pyxis.greenhopper.jira is not a free update like the initial update.

            John Chin added a comment - - edited

            Hi Peter,

            There is a new release of JIRA Agile v6.3.4.3 plugin. Please download it from https://marketplace.atlassian.com/plugins/com.pyxis.greenhopper.jira or update via the Universal Plugin Manager. Also, please see how to updating an add-on to a new version as per document here. Hope this answer your question.

            Thanks,
            John Chin

            John Chin added a comment - - edited Hi Peter, There is a new release of JIRA Agile v6.3.4.3 plugin. Please download it from https://marketplace.atlassian.com/plugins/com.pyxis.greenhopper.jira or update via the Universal Plugin Manager. Also, please see how to updating an add-on to a new version as per document here. Hope this answer your question. Thanks, John Chin

            Petter Larsen added a comment -

            How can we upgrade to 6.3.4.3?

            Petter Larsen added a comment - How can we upgrade to 6.3.4.3?

            Dejan Stojadinović added a comment -

            Surprise, surprise, miracles do happen
            jsheehy mtokar jraoult yilinmo
            Thanks guys and keep up the good work !

            Dejan Stojadinović added a comment - Surprise, surprise, miracles do happen jsheehy mtokar jraoult yilinmo Thanks guys and keep up the good work !

            Vidic Florjan added a comment -

            It looks like workflow does not work as expected (Resolution is still Fixed).

            Vidic Florjan added a comment - It looks like workflow does not work as expected (Resolution is still Fixed).

              Unassigned Unassigned
              yilinmo Yilin (Inactive)
              Affected customers:
              36 This affects my team
              Watchers:
              48 Start watching this issue

                Created:
                Updated:
                Resolved: