-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
1
-
Feature Request: Remove or Increase the 300 Project Limit per Priority Scheme in Jira Cloud
Background & Current Limitation
Jira Cloud’s new Priority Schemes feature allows admins to associate a set of priorities with specific projects, enabling more granular control over issue prioritization. However, there is a hard limit of 300 projects per priority scheme. This is documented in Atlassian’s official release readiness and support documentation:
- Limits per instance:
-
- 300 priorities
-
- 300 priority schemes
-
- 300 priorities in a priority scheme
-
- 300 projects in a priority scheme
-
- 100 project changes to a priority scheme in a single request
This limit applies to both Early Access Program (EAP) and General Availability (GA) releases.
Customer Impact
For large organizations, especially those with hundreds or thousands of Jira projects, this limit creates significant administrative overhead and a poor user experience:
- Fragmentation: Customers must create and manage multiple, nearly identical priority schemes to cover all their projects, leading to configuration sprawl and increased risk of inconsistency.
- Operational Burden: Routine updates (e.g., adding a new priority or changing the default) must be repeated across many schemes, increasing the chance of errors and wasted admin time.
- Migration Pain: Enterprises migrating from Server/Data Center (where such limits may not exist or are higher) face additional hurdles, as their existing configurations cannot be replicated 1:1 in Cloud.
- Customer Sentiment: This limitation is a source of frustration and negative feedback, especially among large enterprise customers who expect scalable, cloud-native administration.
Why Does This Limit Exist?
The 300 project limit is primarily a technical constraint to ensure Jira Cloud’s scalability and performance. Atlassian’s architecture currently relies on a single database instance per tenant, and configuration objects like schemes can become bottlenecks at scale 5. Lower limits help prevent performance degradation and ensure reliable operation for all customers.
Why Should This Be Addressed?
- Enterprise Scalability: Many Atlassian customers operate at a scale where 300 projects per scheme is insufficient. This limit is not aligned with the needs of large organizations and is out of step with the expectations set by other configuration objects in Jira Cloud.
- Cloud Parity: On-premise Jira (Server/Data Center) customers expect feature parity or improvements when migrating to Cloud. Hitting this limit is a blocker for many migrations and undermines the value proposition of Jira Cloud.
- Admin Experience: Reducing configuration duplication and manual effort is a key benefit of scheme-based administration. The current limit negates much of this benefit for large customers.
Proposed Solution
- Increase or Remove the Limit: Raise the project association limit per priority scheme to a higher number (e.g., 1000) or remove it entirely, subject to performance testing and architectural improvements.
- Alternative: Provide a scalable, cloud-native way to manage priorities across large numbers of projects, such as hierarchical or nested schemes, or bulk update tools.
- Communication: If technical constraints require a limit, provide clear guidance, roadmap visibility, and potential workarounds for affected customers.
Supporting Evidence
- The feature request for priorities per project is one of the most voted and watched tickets in Atlassian’s history, with over 5,000 votes and 300,000+ impacted seats.
- Post-migration experience for Jira Cloud has declined due to missing or limited functionality, including this limitation.
- The current workaround (creating many similar schemes) is not sustainable for large organizations and leads to negative customer sentiment.
Summary:
The 300 project limit per priority scheme in Jira Cloud is a significant blocker for large customers and creates unnecessary administrative complexity. Addressing this limitation—by raising or removing the cap, or providing scalable alternatives—would greatly improve the experience for enterprise customers and support broader adoption of Jira Cloud.
Sources
- [Manage priority schemes | Atlassian Support|https://support.atlassian.com/jira-cloud-administration/docs/manage-priority-schemes/]