---
title: "Set the Default Maximum Issue Limit"
canonical: "https://support.appfire.com/space/DHDC/2802650530/Set%20the%20Default%20Maximum%20Issue%20Limit"
format: markdown
---
## Overview

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

| **Host** | **Gadget** | **Limit** | **Dynamic filter** |
| --- | --- | --- | --- |
| [data center] | All (Jira) | - Default 2,500
- Up to limit set by admin [500 - 10,000] | :check_mark: |
| [cloud] | [https://appfire.atlassian.net/wiki/spaces/DHDC/pages/2802655624](https://appfire.atlassian.net/wiki/spaces/DHDC/pages/2802655624) | - Default 2,500
- Up to limit set by admin [500 - 10,000] | :cross_mark: |

> 📝 [https://appfire.atlassian.net/wiki/spaces/DHDC/pages/2802655624](https://appfire.atlassian.net/wiki/spaces/DHDC/pages/2802655624): 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.

<details>
<summary>Supported fields:</summary>

## 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.
</details>