NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Some users are experiencing a problem with JIRA gadgets, when effected no gadgets (except the Introduction gadget) load, and error messages are displayed:

      "This gadget cannot be displayed on your dashboard. This could be due to a licensing problem or an application error. If you need this gadget, contact your administrator for assistance. Otherwise, you can remove it from your dashboard."

      When attempting to add a new gadget to the dashboard, only the Introduction gadget is listed.

      Errors appear in the logs for example:

      /secure/Dashboard.jspa [c.a.g.renderer.internal.GadgetSpecFactoryImpl] Error occurred while retrieving gadget spec for rest/gadgets/1.0/g/com.atlassian.streams.streams-jira-plugin:activitystream-gadget/gadgets/activitystream-gadget.xml
      /secure/Dashboard.jspa [c.a.g.embedded.internal.GadgetUrlBuilder] GadgetUrlBuilder: could not parse spec at rest/gadgets/1.0/g/com.atlassian.streams.streams-jira-plugin:activitystream-gadget/gadgets/activitystream-gadget.xml
      

      Workaround

      P.S: Instances affected by this bug have also reported problems on:

      • Viewing agile boards with a filter with more than 1 project
      • Service desk email handler can't retrieve emails (the connection log shows an error)

            [JRASERVER-45494] No gadgets load in JIRA, unable to add new gadgets

            This error occurs with version 9.6.0 as well. 
            I wish you find a solution to this matter soon.

            Juliman Gea added a comment - This error occurs with version 9.6.0 as well.  I wish you find a solution to this matter soon.

            I am working on Jira v8.13.4 and am facing this issue. Is there a permanent solution for this? Because It's happening again and again and we cannot restart Jira everytime to resolve it.

            Gaurav Arora added a comment - I am working on Jira v8.13.4 and am facing this issue. Is there a permanent solution for this? Because It's happening again and again and we cannot restart Jira everytime to resolve it.

              Unassigned Unassigned
              mpaisley Mel Paisley
              Affected customers:
              3 This affects my team
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: