Every day we are facing a bug in the jira, whenever we create a new Task and create the link with an "Epic" the error appears in "Epic" and we are blocked to create new cards.
Every day we make the corrections and the error returns.
What could be causing this error?
Follow the image with the error.
You stated you make the changes everyday and the issue returns. Are you following the guidance in the knowledge base article Issue screen displays error rendering greenhopper-epics-issue-web-panel:
The following SQL query will search for any invalid epic links in your instance of JIRA:
SELECT * FROM issuelink il WHERE il.LINKTYPE = ( SELECT id FROM issuelinktype WHERE linkname = 'Epic-Story Link') AND ( il.destination IS NULL OR il.SOURCE IS NULL OR not exists (SELECT null FROM jiraissue ji where ji.id = il.destination) OR not exists (SELECT null FROM jiraissue ji where ji.id = il.source) );
If the query above returns any results, proceed to the Resolution to remove the invalid epic links.
Follow the instructions from Using the database integrity checker:
Through the database:
- Shutdown JIRA;
- Create a database backup;
Execute the following query to remove the corrupt entry:
delete from issuelink il WHERE il.LINKTYPE in ( SELECT id FROM issuelinktype WHERE linkname = 'Epic-Story Link') AND ( il.destination IS NULL OR il.SOURCE IS NULL OR not exists (SELECT null FROM jiraissue ji where ji.id = il.destination) OR not exists (SELECT null FROM jiraissue ji where ji.id = il.source) );
If the SELECT query from Diagnosis taking too long, the DELETE query can be replaced with the correct ID returned from the SELECT query as alternative.
If you've followed those steps the next thing you'd need to figure out is why this is occurring. According to Issue screen displays error rendering greenhopper-epics-issue-web-panel:
This situation is usually seen when having Transition Post Functions that update values. Plugins like "JIRA Suite Utilities" provide additional functionality that it may fail depending on conditions when they are executed. For example, adding an Epic Link to an Epic. This will exit the Creation process and leave an inconsistency on issues. Make sure the "Creates the issue originally." Post Function is first in the Create transition.
Try the above steps and check for any post functions that could be causing this issue and let me know the outcome.
I would look at the application log (on disk) when the error is happening. There should be a stack trace there with more information. It would also be worth using the built-in Log Scanner to see if it finds problems with your system.
Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...
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