Problem Definition

Related to JSWSERVER-15051 and JRASERVER-65602
JIRA will have memory pressure (and may hit OOME) in case user creates board with filter with large number of issues (20k+). This might lead to performance problems at busy instance.
While ticket JRASERVER-65602 focuses on empty filter to prevent simple mistakes, it's possible to create filter with large result set.

Suggested Solution

Create a new application variable BOARD_ISSUES_COUNT_LIMIT (suggested default value 5000), similar to jira.bulk.edit.limit.issue.count in jira-config.properties

While opening any board or changing board filter, check the issues count return by board filter and compare it with BOARD_ISSUES_COUNT_LIMIT.

• Display board only when it has less issues than limit.
• Display warning message if condition fails and redirect users to contact Jira admins.
  • see also related JRASERVER-66791

The request should be part of the Jira Software guardrails to be able to limit the number of issues in the board instead of depending very much on the board filter (eg. JQL filter) to limit the issue numbers which causing much more works for user admin to identify the large number of issues.

Workaround

None