Create Limits and Warnings on too many Issue Security Levels

Summary

Creating too many issue security issues can create some serious performance issues within JIRA. Limit or at least warning the customer that they are about to run into this issue when creating more than the recommend number of Issue Security Levels within the product could prevent customers from making an implementation decision that causes negative performance impacts within their environment and a poor experience of JIRA.

Environment

JIRA + Many Issue Security Levels.

Steps to Reproduce

1. Create Many Issue Security Levels as per: Configuring Issue-level Security
2. Exceed the recommended limit of ten Issue Security Levels.
3. Observe degradation of JIRA performance as a result of this.

Expected Results

We should at least warn the customer that using too many issue security levels will potentially impact JIRA performance, and if possible implement both soft and hard limits on the number of issue security levels that can be created. There could also be the possibility of allowing these values to be set with flags so that the limitation can be knowingly breached.

Actual Results

The current implementation relies on customers reading the recent versions of the Documentation that highlight this performance issue. This doesn't work for a few reasons:

• Users that are 'old hat' or confident with the product functionality might not consult the documentation.
• User that have implemented one or two issue security levels, my erroneously think the feature can support many more levels without consulting the documentation
• Users that are finding the functionality might not consult the documentation.