Issue Security Timeout on large Projects

Summary:

Following the Process outlined here:

• https://confluence.atlassian.com/display/Cloud/Configuring+Issue-level+Security

When Applying an Issue Security Scheme to a project >400-500 issues causes a timeout to occur, and displays a blank screen eventually leading to a XRSF missing security token page.

Steps to Reproduce

1. Apply Issue level security to a large project containg ~>400 issues

Expected

Operation completes successfully

Actual

After ~60 seconds the page will timeout

If One of the following functions is initiated it can cause Other Errors to occur and the Instance Stops the progress of the Bulk operation and will leave some issues assigned to the scheme and others are not:

• the Page is Refreshed before the XRSF token Error
• Re-index is run
• Attempt to run a second issue security association to the project

The above operations can lead to locking out all users From accessing the Tickets additional steps are needed if this occurs there are additional steps needed to fix detailed in this Knowledge-Base Article

• https://confluence.atlassian.com/display/JIRAKB/Issue+Security+Levels+Locks+Issues+From+All+Users

Workaround:

1. open two tabs first tab issue security for the project and the other issue navigator with the Query project = <DESIRED_PROJECT> AND level is EMPTY
2. Apply a Issue Security Scheme that causes a timeout at 60 seconds
DO NOT RUN ANY OF THESE OPERATIONS until it completes the bulk assignment:

• Running a re-index
• Reloading the page after the timeout occurs
• Attempting to run a new issue security association.

3. Even though the timeout occurs in the UI the operation continues in the background

• to track the progress use following JQL query In Issue Navigator after adding the security column to the issue navigator view. (Note that the security level is noted by the JQL LEVEL):

  project = <Desired Project> AND level is EMPTY
  

4. once it no longer reruns results the operation is complete.

• You can also run the following to confirm all issues associated properly:
  project = <Desired Project> AND level is not EMPTY

5. When it completes run a full lock and re-index of the system to clear out all erroneous caching caused by the timeout. as the association will only display 50% of the time in the Issue security scheme unless the index is rebuilt.