Users get the Script error message when trying to access JIRA Agile Board using IE version 11. Some users will get Avatar ID error when accessing it using Firefox, Chrome and Safari

      Steps to reproduce:
      1 Try to access JIRA Agile Board using IE version 11, some users will get Script Error message.
      2. Notice the error appears

      Version
      6.6.11-D20141024T064516

      Sample Errors:

      An error occurred
      
      Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues.
      
      Details
      1.â—¦Exception: Attribute 'avatarId' does not exist
      â—¦Resource: https://<instance-name>/s/fde4729079c84dcd1a682e003e388f91-CDN/en_US-xr35dg/64005/36/d20473d5b101a3367db78486a16f8219/_/download/contextbatch/js/gh-rapid,-greenhopper-rapid-non-gadget,-atl.general/batch.js?jag_disabled_marketing=true&locale=en-US
      â—¦Line: 7683
      
      Environment
      
      Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; .NET4.0E; .NET4.0C; .NET CLR 3.5.30729; .NET CLR 2.0.50727; .NET CLR 3.0.30729; ASU2JS; rv:11.0) like Gecko
      
      An error occurred
      
      Please try refreshing the page, or contact your administrator / Atlassian Support if the problem continues.
      
      Details
      1.â—¦Exception: Script error
      â—¦Resource: https://d2p4ir3ro0j0cb.cloudfront.net/<instance_name>/s/a55dc1a84bb64204909278bc4f32a0ee-CDN/en_UK8r2ia8/64005/36/8cc8bd72edd525324b5a64951b92dbfd/_/download/contextbatch/js/gh-rapid,-greenhopper-rapid-non-gadget,-atl.general/batch.js?jag_disabled_marketing=true&locale=en-UK&analyticsEnabled=true
      â—¦Line: 0
      
      Environment
      
      Mozilla/5.0 (Windows NT 6.3; WOW64; Trident/7.0; .NET4.0E; .NET4.0C; .NET CLR 3.5.30729; .NET CLR 2.0.50727; .NET CLR 3.0.30729; ASU2JS; rv:11.0) like Gecko
      

      Possible Workaround:

      • Avatar ID error message: Use a different browser (ie Firefox or Chome) and set a new avatar for the User Profile. This will allow IE11 users to access the Board normally again. This workaround only works for some instances.
      • Script Error:
        1. Disable the "jira-inline-issue-create-plugin" plugin:
        2. As a JIRA administrator, visit the add-on manager (Administration area >> Add-ons tab >> Manage add-ons).
        3. Search for "jira-inline-issue-create-plugin".
        4. Expand the plugin section.
        5. Click "Disable".
      • Side-effect: This will disable the 'Create Issue' widget under each sprint section in Plan Mode. Users can still create issues using other means.
      • Note that this add-on will be automatically enabled again by Atlassian when the fix is ready. If you have any trouble with the workaround please contact Support.

            [JSWSERVER-11411] Script errors when accessing Agile Board

            dsamuelson880937257 added a comment -

            Hi Kiran,

            I already did create a support ticket and the resolution was to send me to this closed issue.

            dsamuelson880937257 added a comment - Hi Kiran, I already did create a support ticket and the resolution was to send me to this closed issue.

            Hi Dsamuelson880937257,

            This issue is a symptom of GHS-11418 and has been resolved along with GHS-11418. If you are still facing this issue, I request you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security. The credentials to access the Support site should be the same as this one (jira.atlassian.com).

            Regards,
            JIRA Software

            Kiran (Inactive) added a comment - Hi Dsamuelson880937257 , This issue is a symptom of GHS-11418 and has been resolved along with GHS-11418 . If you are still facing this issue, I request you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security. The credentials to access the Support site should be the same as this one (jira.atlassian.com). Regards, JIRA Software

            dsamuelson880937257 added a comment -

            Same question - why is this marked as resolved? It is not resolved and is still an issue.

            dsamuelson880937257 added a comment - Same question - why is this marked as resolved? It is not resolved and is still an issue.

            That workaround is not a reasonable solution - "Side-effect: This will disable the 'Create Issue' widget under each sprint section in Plan Mode. Users can still create issues using other means."

            Why is this marked as Resolved?

            Brock Newitt added a comment - That workaround is not a reasonable solution - "Side-effect: This will disable the 'Create Issue' widget under each sprint section in Plan Mode. Users can still create issues using other means." Why is this marked as Resolved?

            workaround posted on GHS-11418 (i.e. disabling the "jira-inline-issue-create-plugin" plugin) worked for me.

            Vincent den Breejen added a comment - workaround posted on GHS-11418 (i.e. disabling the "jira-inline-issue-create-plugin" plugin) worked for me.

            Ryan Slye added a comment -

            I'm getting same error on IE ver 9.0.32.

            Ryan Slye added a comment - I'm getting same error on IE ver 9.0.32.

            Hi all,

            Apologies for the lack of clarification on the status of this bug and the hassle it has caused. Our development team identified this bug to be originated from the same root cause of GHS-11418, hence, the progress of both problem will be tracked via GHS-11418 from now on. While awaiting for the official fix, we also have a new workaround which would work for both problem, posted on GHS-11418 (i.e. disabling the "jira-inline-issue-create-plugin" plugin). If you have trouble with the workaround please contact Support for further assistance.

            Best regards,
            Azwandi
            OnDemand Support

            Azwandi Mohd Aris (Inactive) added a comment - Hi all, Apologies for the lack of clarification on the status of this bug and the hassle it has caused. Our development team identified this bug to be originated from the same root cause of GHS-11418 , hence, the progress of both problem will be tracked via GHS-11418 from now on. While awaiting for the official fix, we also have a new workaround which would work for both problem, posted on GHS-11418 (i.e. disabling the "jira-inline-issue-create-plugin" plugin). If you have trouble with the workaround please contact Support for further assistance. Best regards, Azwandi OnDemand Support

            We're getting the error on IE 10 but not on Chrome

            Vikki Short added a comment - We're getting the error on IE 10 but not on Chrome

            We are also experiencing this error on Firefox and in the 'Work' mode of the Storyboard. This error has also occurred when one of my colleagues has uploaded an attachment to an issue.

            Paul Bremeyer added a comment - We are also experiencing this error on Firefox and in the 'Work' mode of the Storyboard. This error has also occurred when one of my colleagues has uploaded an attachment to an issue.

            Casey B added a comment -

            I know Service Desk is new to Atlassian but this is no excuse for the Service Management, or lack there of, displayed in the handling of this issue. Incidents relate to problems and shouldn't be closed as a duplicate incident unless related to a problem record. Also, closing the incident that clearly has more followers and votes doesn't make much sense.

            I have no doubt the issue is being addressed internally but I suggest a review of the Service Management related to this issue once closed to prevent the less than ideal customer service experience.

            Casey B added a comment - I know Service Desk is new to Atlassian but this is no excuse for the Service Management, or lack there of, displayed in the handling of this issue. Incidents relate to problems and shouldn't be closed as a duplicate incident unless related to a problem record. Also, closing the incident that clearly has more followers and votes doesn't make much sense. I have no doubt the issue is being addressed internally but I suggest a review of the Service Management related to this issue once closed to prevent the less than ideal customer service experience.

              Unassigned Unassigned
              rsaputra Adven
              Affected customers:
              7 This affects my team
              Watchers:
              38 Start watching this issue

                Created:
                Updated:
                Resolved: