I am getting "An exception occured while rendering the web panel: com.pyxis.greenhopper.jira:greenh"

[Pallav Ladekar]

getting this  "An exception occurred while rendering the web panel: com.pyxis.greenhopper.jira:greenhopper-epics-issue-web-panel (null)"  error when trying to clone issue.

gone through  "https://confluence.atlassian.com/jirakb/issue-screen-displays-error-rendering-greenhopper-epics-issue-web-panel-779158857.html"  link  but I am not found any  "entries for Epic links within the database are invalid/corrupted."

is there any suggestion to resolve this issue.

[Andy Heinzer · Accepted solution]

Hi Pallav,

I understand you are getting this error above when trying to clone an issue.  However it sounds like the KB you listed does not actually apply to you here since the SQL query did not return any results.

I have searched some other support tickets with this error, and I think I have found a pattern here.  While a corrupt epic link can cause this as described in the KB, it appears that there can be other causes.  Chief among them could be if there is corruption in the database, specifically in regards to the lexorank field that Jira Software uses to rank issues.  When this rank field does not have exactly two markers, lots of functions can fail in Jira, such as deleting issues, reindexing, exporting, or moving issues.

I'm not sure if you are seeing any of these other related problems or not, but if you were there would also be an error like this in the atlassian-jira.log file:

Caused by: java.lang.RuntimeException: Expected exactly 2 rows; the maximum marker row and the lowest ranked row for rank field[id=10300]

I'd be interested if you can find this error in your logs when trying to move or delete an issue in Jira.  If you do, then I'd recommend following Cannot reindex jira due to Expected exactly 2 rows the maximum marker row and the lowest ranked row for rank field.  It has a comprehensive set of steps to follow to identify the exact cause here and steps to correct it.

Try this and let me know the results.

Andy

[Pallav Ladekar]

Hi Andy,

Thanks for the reply.  You were right, the issue was with  "lexorank field"  there was no field in the lexorank schema,  so  I added it manually.

INSERT INTO "AO_60DB71_LEXORANK" ("FIELD_ID", "ISSUE_ID", "LOCK_HASH", "LOCK_TIME", "RANK", "TYPE") VALUES (10900, -9223372036854775808, null, null, '0|000000:', 0);
INSERT INTO "AO_60DB71_LEXORANK" ("FIELD_ID", "ISSUE_ID", "LOCK_HASH", "LOCK_TIME", "RANK", "TYPE") VALUES (10900, 9223372036854775807, null, null, '0|zzzzzz:', 2);

 and it's working fine now.

[Kuldeep Singh]

Hi,

I have tried the query, it shows 01 updated,

but issue remains same. i am having exact same issue.

Thanks,

Kuldeep