Summary

Jira issues are not viewable. The following error appears when trying to access an issue in a project with added Issue Security:

"It seems that you have tried to perform an operation which you are not permitted to perform."

There are no entries for Users / Groups / Project Roles when you Edit Issue Security Levels. Or, after adding users or groups the same error appears.

Manually remove issue security from the Jira Database

1. Locate the affected tables with this command (Project ID will vary):

   1. jira=> SELECT id,project,security,issuenum FROM jiraissue where project = 10000;
        id   | project | security | issuenum 
      -------+---------+----------+----------
       15425 |   10000 |          |        1      <<< test issue with no issue level security set
       12317 |   10000 |    10001 |        2      <<< issue not showing up (locked issue) with security value assigned to no one Including sysadmin
      (2 rows)

2. Remove the Security from the affected rows
   1. For a single Issue:

   2. UPDATE jiraissue SET security = NULL WHERE id  = **Put ID Here** AND issuenum = **put IssueNum Here**;

   3. For an entire project:

   4. UPDATE jiraissue SET security = NULL WHERE project = **put Project here**;

You can now add users or groups to the Issue Level Security settings, and assign to a project.

Please reference the documentation: Configuring Issue-level Security

Cause: Large number of issues associated to issue security simultaneously

This can occur when you assign the security level to a Project before you add any Users or Groups.  

There's a problem with associating a large number of issues to a security scheme at the same time. Currently, we have only seen this occur on instances associating projects with ~400 or more issues.

Please see the related bug: JRASERVER-43038 Issue Security Timeout on large Projects

The error occurs after the timeout and one of the following operations occurs causing the association to fail and no groups, or users get set for the security policy:

• Reindex
• Refresh the page while timed out
• Running the same association a second time while the other association is occurring in the background and not visible in the UI

Related resources

• See JRASERVER-40231 - Unexpected Behavior in attempting to apply Issue Security Scheme
• See JRASERVER-32546 - Bulk operation with over 300 issues time out and display Down for Maintenance page while is still running in the background