We recently upgraded to JIRA Agile 6.2.2 and are getting these errors when opening issues.
Error rendering 'com.pyxis.greenhopper.jira:greenhopper-epics-issue-web-panel'. Please contact your JIRA administrators.
Error rendering 'com.atlassian.jira.jira-view-issue-plugin:details-module'. Please contact your JIRA administrators.
Our IT team has attempted a few different approaches to fix the issue including ensuring we're on the latest versions of Java, JIRA, and plug-ins. But we haven't been able to resolve.
In our logs, we're getting references to errors indexing custom field customfield_10505 which happens to be our Sprint field. Any suggestions?
Hi Scott, I found a similar case in our support history and in that case the problem was corrupted entry in the database.
Try to execute this query:
select * from issuelink where linktype = (select id FROM issuelinktype where linkname = 'Epic-Story Link') AND destination NOT IN (SELECT id FROM jiraissue) or destination is null OR source NOT IN (SELECT id FROM jiraissue) or source is null;
In case it return anything create a backup of your database and remove the entry.
To everyone trying to access the article mentioned by Tiago, it has been moved from the GreenHopper Confluence Space to the Agile Confluence space: https://confluence.atlassian.com/display/AGILEKB/Issue+screen+displays+error+rendering+greenhopper-epics-issue-web-panel
Hi Danilo, Thank you for reply! Actually, here are two different issues, looking similar: 1. Broken link between Epic and deleted issue (issue from KB), linktype = "Epic Story Link" 2. Orphaned sub-tasks with existing link "jira_subtask_link" and deleted parent, and field Sprint, it became crazy in this situation. (issue from this question). Deleting link using Integrity Checker tool didn't solved this issue in my case, only faking parent link did (see my answer to this question). Both cause errors on rendering issue view, but they are different issues.
Just hit this issue with sub-task without parent and Sprint field.
Thanks to answers to this question and @Jamie Echlin [Adaptavist] 's Script Runner - I was able to resolve similar issue.
After these steps I was able to remove the sub-task and its new parent.
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
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