We recently upgraded Jira and Jira Agile. After the upgrade, Jira agile gadgets on the dashboard are no longer available. The following warning can be found in the logs:
/secure/Dashboard.jspa [gadgets.renderer.internal.GadgetSpecFactoryImpl] Error occurred while retrieving gadget spec for rest/gadgets/1.0/g/com.pyxis.greenhopper.jira:greenhopper-gadget-sprint-burndown/gadgets/greenhopper-sprint-burndown.xml
The following is seen in the UI:
Error loading gadget from rest/gadgets/1.0/g/com.pyxis.greenhopper.jira:greenhopper-gadget-project-dashboard/gadgets/greenhopper-project-dashboard.xml: org.apache.shindig.gadgets.GadgetException: Unable to retrieve gadget xml. HTTP error 404
System as been re-indexed and restarted.
I have raised an issue with Atlassian support - but I'm trying out here as well.
I believe you are facing the problem described on this bug:
Below you can see the same SQL query from one of our test instances affected by the same issue. Note that we have one extra line, which is exactly the one mentioned in the Bug above:
After test the suggested workaround in the bug, everything seems to be working here, but I strongly suggest you to create a test instance for that, since we will modify the database directly. Also, database modifications need to be done with JIRA down, so a test instance will be easier for that, right?
Basically, you need to run the following queries in your JIRA database:
INSERT INTO propertyentry VALUES ((SELECT seq_id FROM sequence_value_item WHERE seq_name = 'OSPropertyEntry'), 'GreenHopper.properties', 1, 'GreenHopper.JIRA60.Version.Migration', 1); INSERT INTO propertynumber VALUES ((SELECT seq_id FROM sequence_value_item WHERE seq_name = 'OSPropertyEntry'), 1); UPDATE sequence_value_item SET seq_id = (SELECT seq_id FROM sequence_value_item WHERE seq_name = 'OSPropertyEntry') + 10 WHERE seq_name = 'OSPropertyEntry';
I hope it helps.
Thank you @Pedro; I got this information from the first Hercules report (before the restart of the server and cleaning the logs) as well. However, I disregarded it due to this comment: "If this returns more than 5k records you may be affected by this bug".
We have 212 fixVersions, not > 5K.
The bug is also reported for 6.0?
Every team in the world is unique, and so Atlassian believes that each and every team's best way of working needs to be molded to their unique circumstances – ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot