JIRA issue doesn't exist or you don't have permission to view it.

[Dan Lohaus · Accepted solution]

All,

Wanted to provide an update....

Based on information Janet provided above, I looked at the table associated with field configuration. I found that the Field Configuration and FieldConfigSchemeIssueType tables had some anomalies. Even though the JIRA Database Integrity Checker passed with no errors, I had identified duplicate rows in the FieldConfiguration table and corresponding rows within the ...IssueType table that were of concern.

In the ...IssueType table there were 5 record referencing to 5 issue type 2 with the same field configuration and configuration scheme. The other three and 3 different configurations pointing to the 3 extra rows in the FieldConfiguration table with the same configuration scheme. The 2 fields I was having problems with showed this same pattern.

After sending logs and snippets to Atlassian Support there request for me to send the database which was not possible due to customer wishes. I asked for help from another JIRA administrator and conferred with him about options. We chose to make the changes to the underlying database. Backups were made, changes made, and all is resolved.

I do not know how the table got in the state that they were but I suspect that in performing import after import and making changes to fields, I may have skipped a reindex or something after a change and the import added the extra rows.

If anyone wants further information, you can contact me at dan.lohaus@ngc.com

[Dan Lohaus]

All,

Wanted to provide an update....

Based on information Janet provided above, I looked at the table associated with field configuration. I found that the Field Configuration and FieldConfigSchemeIssueType tables had some anomalies. Even though the JIRA Database Integrity Checker passed with no errors, I had identified duplicate rows in the FieldConfiguration table and corresponding rows within the ...IssueType table that were of concern.

In the ...IssueType table there were 5 record referencing to 5 issue type 2 with the same field configuration and configuration scheme. The other three and 3 different configurations pointing to the 3 extra rows in the FieldConfiguration table with the same configuration scheme. The 2 fields I was having problems with showed this same pattern.

After sending logs and snippets to Atlassian Support there request for me to send the database which was not possible due to customer wishes. I asked for help from another JIRA administrator and conferred with him about options. We chose to make the changes to the underlying database. Backups were made, changes made, and all is resolved.

I do not know how the table got in the state that they were but I suspect that in performing import after import and making changes to fields, I may have skipped a reindex or something after a change and the import added the extra rows.

If anyone wants further information, you can contact me at dan.lohaus@ngc.com

[Dan Lohaus]

I apologize. My query statement was incorrect. It returned 5 rows with a value in each of the issuetype fields.

[Dan Lohaus]

Thanks for the response Janet. I receive 0 rows returned on the seecond query.

I assume this is bad.

[Janet Albion]

Hi Dan,

Tried the following SQL query to check if the custom field is associated to Any Issue Type or 5 Issue Types in database level:

1. check the customfield id

select id from customfield where cfname='<customfield_name>';

2. then:

select * from fieldconfigschemeissuetype where fieldconfigscheme in (select FIELDCONFIGSCHEME from configurationcontext where customfield='customfield_ID');

note: If the custom field is map to Any Issue Type, the ISSUTYPE column will have NULL value.

I would recommend creating a support ticket if this require further checking in the database as i am suspecting there is database inconsistency that might cause this.