How to set the default maximum issue limit

Overview

This help document guides users through setting the default maximum issue limit in Jira's administration settings.

 

 

Setting the default maximum issue limit

  1. Navigate to Jira administration.

  2. Click Manage apps.

  3. Choose Global settings.

  4. Select Performance options.

  5. Under Set issue limit, pick the maximum number of issues.

  6. Click Save.

image-20240614-203920.png
Admins can set a minimum of 500 to a maximum of 10,000 issues

 

Host

Gadget

Limit

Dynamic filter

Host

Gadget

Limit

Dynamic filter

data center

All (Jira)

  • Default 2,500

  • Up to limit set by admin [500 - 10,000]

cloud

Jira Custom Charts

  • Default 2,500

  • Up to limit set by admin [500 - 10,000]

Jira Custom Charts: Previews of tables are limited to 100 issues and to 1,000 issues to avoid hindering Jira performance.

Dynamic Filter Limitation

This limitation only affects Cloud instances.

The dynamic filter in Dashboard Hub is optimized to handle gadgets with up to 2,500 issues, ensuring optimal performance and smooth functionality of the dashboard features. Gadgets displaying information that requires more than 2,500 won’t be affected by the dynamic filter bar.

Users can overcome this by refining JQL statements in gadgets to precisely filter issues based on criteria like type, status, assignee, and labels. This optimization helps manage performance and ensures responsive, customizable dashboards within Dashboard Hub.

Number of Issues Processed

The system is optimized to process up to 2,500 issues per gadget for optimal performance. While it is possible to set a higher maximum issue limit (as indicated above), the effective processing capacity may not exceed this number due to several factors (see table above):

  • The gadget is designed to support up to a specific number of results.

  • The data is displayed in a table rather than a chart (charts allow more issues).

  • Certain data, such as custom fields from other applications, may not be supported in large volumes.

  • Queries have fields that are not currently supported.

System fields

  • Affects versions

  • Assignee

  • Attachment

  • Comment

  • Components

  • Created

  • Creator

  • Description

  • Due date

  • Environment

  • Fix versions

  • Images

  • Issue Type

  • Key

  • Labels

  • Last Viewed

  • Linked Issues

  • Log Work

  • Original estimate

  • Parent

  • Priority

  • Progress

  • Project

  • Remaining Estimate

  • Reporter

  • Resolution

  • Resolved

  • Restrict to

  • Security Level

  • Status

  • Status Category

  • Status Category Changed

  • Sub-tasks

  • Summary

  • Time Spent

  • Time tracking

  • Updated

  • Votes

  • Watchers

  • Work Ratio

  • Σ Original Estimate

  • Σ Progress

  • Σ Remaining Estimate

  • Σ Time Spent

Custom Fields

Any custom field type, with any of the following schema.type:

  • date

  • datetime

  • number

  • project

  • string

  • user

  • version

  • option

  • sprint

And array of the above.

 

Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.