nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Error following upgrade of JIRA Agile

ScottW_2osyuu

We recently upgraded to JIRA Agile 6.2.2 and are getting these errors when opening issues.

greenhopper-epics-issue-web-panel

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

details-module

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?

Accepted answers

Tiago Comasseto

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.

Cheers

All comments

Tiago Comasseto

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.

Cheers

ScottW_2osyuu

Thank you. We got some results. It looks like the problem is related to some sub-tasks that didn't get deleted when the parent was deleted. How do I remove the orphaned sub-tasks?

Tiago Comasseto

Hi, we have a KB article to this issue here. Basically the corrupted entries need to be removed.

Cheers

ScottW_2osyuu

Worked like a charm. Thanks!

Denis Yaparov1

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.

I created new issue in the same project
I added a link between new issue and the sub-task
In DB I changed link's type, source ID and destination ID. Sub-task's ID must be in destination column
Using Script Runner I cleared Jira's cached data

After these steps I was able to remove the sub-task and its new parent.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

jira-administration