issue link does not have a destination issue number

[Andrew Thorne]

I have been trying to write a Groovy script that will set the Epic Link to a value if no value is given when the issue is created. During the development, which I had to do in production because we have not had a test environment since we merged our two JIRA systems last year, my script suffered from many fails.

Afterwards, when I tried to check the issue I was trying to link to, there was an error on the issue browse screen that read:

greenhopper-epics-issue-web-panel

Error rendering 'com.pyxis.greenhopper.jira:greenhopper-epics-issue-web-panel'. Please contact your JIRA administrators.

Searching the internet for this error, lead me to this page:

https://confluence.atlassian.com/jirakb/issue-screen-displays-error-rendering-greenhopper-epics-issue-web-panel-779158857.html

I ran the SQL in the diagnosis section and found an issue link from the issue I was trying to link to but with a destination issue number that was null.

I sent all this information to our infrastructure guys but they are not keen on implementing the solution that is in the web page as it is for JIRA version 7.8 and we have version 7.3.6.

Does anybody know of any other method to resolve this error? Or if the instructions on this web page would still work with our version?

Thanks for any advice you can give.

[Adrián Plaza [DEISER] · Accepted solution]

Hi @Andrew Thorne

The solution of the KB that you expose must work for your version of JIRA too, but first of all, do a database dump and then try to execute the SQL to delete the broken link.

Cheers,
Adrián.

[RTwo_Dtwo]

If 

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) 
);

Result 0

Then:

insert into "AO_60DB71_LEXORANK" ("BUCKET","FIELD_ID","ID","ISSUE_ID","RANK","TYPE") VALUES (0,10005,7,-9223372036854775808,'0|000000:',0);
insert into "AO_60DB71_LEXORANK" ("BUCKET","FIELD_ID","ID","ISSUE_ID","RANK","TYPE") VALUES (0,10005,8,9223372036854775807,'0|zzzzzz:',2);

[Alexis Baker]

We've experienced this issue just now, in order to resolve the issue, we created the new Epic, created a new story, then related the existing sub tasks to that new story, and the new story to the new epic.

The story with the issue wasn't possible to close, but we cycled to closed resolved.

Saved on restarting DB, and admin!

Cheers, 

Alexis