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

    • 5
    • 3
    • Hide

      Atlassian Update – 27 March 2025

      Dear Customer,

      We understand that this suggestion is important to you due to the performance challenges you are facing however we are closing it as we do not have plans to invest into supporting large size of issues on the AgileBoards.
      The large numbers of issues as well as comments, attachments or links to them might cause significant performance challenges and we strongly recommend to optimize in this area.
      Please refer to the Performance and Scaling recommendations for more details about Jira Software Guardrails.

      Kind regards,
      Beata Kupiec, Principal Product Manager, Enterprise Data Center

      Show
      Atlassian Update – 27 March 2025 Dear Customer, We understand that this suggestion is important to you due to the performance challenges you are facing however we are closing it as we do not have plans to invest into supporting large size of issues on the AgileBoards. The large numbers of issues as well as comments, attachments or links to them might cause significant performance challenges and we strongly recommend to optimize in this area. Please refer to the  Performance and Scaling  recommendations for more details about  Jira Software Guardrails. Kind regards, Beata Kupiec, Principal Product Manager, Enterprise Data Center
    • 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.

      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

              a1b3d2f3fbef Beata Kupiec
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              24 Vote for this issue
              Watchers:
              28 Start watching this issue

                Created:
                Updated:
                Resolved: