Issue is not accessible

[Radha Khullar]

Jira issue was created by an event listener but due to permission issue condition on workflow, the transition failed and now the issue is not accessible.

I can see the issue listed under issue navigator as part of project jql 

project = "PP"

Clicking on the 3 dots ... for an issue fails with:

There were errors loading the issue.

And searching the issue with issuekey fails with :"An issue with key 'XX' does not exist for field 'issuekey'

Below error was faced while automatic issue creation using event listener:

org.ofbiz.core.entity.generictransactionexception: commit failed, rollback previously requested by nested transaction.

Can someone please help resolve this issue.

Thanks.

[Andy Heinzer]

Given what you have stated so far, I'm not sure that the issue actually exists in Jira's database.  If it doesn't exist there, then it really doesn't exist in Jira.   The odd part here is that you stated you can see the issue in the search results, is that correct?   I would not expect that you would see this in the search results of Jira unless the issue did exist in the database.

My thought here is that perhaps somehow the event listener was able to temporarily create the issue, just long enough for Jira to start to reindex the change on that issue.  But then somehow the database transaction for the creation of the issue appears to have been rolledback at the database level.  If the issue isn't the database, I don't see what can be done to recover it at this point.

I would want to go to the database itself to see what issues exist there for this project.  You could use a SQL query like this one for postgres:

select  p.pkey || '-' || ji.issuenum as IssueKey, *  from jiraissue ji
join project p on p.id = ji.project
where p.pkey='PP' order by issuenum desc;

This should return a list of all the issues in project key PP in a descending order.