Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-16546

As an JIRA Software Administrator I want to limit number of issues per board to prevent resource overuse

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • AgileBoard
    • 1
    • 3
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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.

      Workaround

      None

            Unassigned Unassigned
            ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
            Votes:
            14 Vote for this issue
            Watchers:
            18 Start watching this issue

              Created:
              Updated: