-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Plans - Timeline
-
0
-
83
Hi everyone,
We’ve split the original request in https://jira.atlassian.com/browse/JRACLOUD-89221 into two separate tickets so we can track the different “limits” independently:
JRACLOUD-89221 – Issue limit per plan (now increased to 10,000 issues and resolved as completed).
JRACLOUD-97317 – Project limit per plan (this ticket).
This ticket will now be the primary place where we track work related to raising the maximum number of projects that can be included in a plan.
We are currently investigating the implementation of this: evaluating performance and stability implications of higher project counts, identifying safe new limits, and designing the right UX and safeguards so larger plans remain usable.
If increasing the project limit is important for your use case, please vote for and watch this ticket so we can better prioritise and keep you updated as we make progress.
Joe
Product Manager-Jira Cloud
jnguyen2@atlassian.com
NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding suggestion.
Problem Definition
Currently there is an upper limit of 100 Project and 5000 open issues per plan due to performance restriction.
![]()
Suggested Solution
We want to make this more scalable and allowing more project and issues per plan to support larger clients.
Workaround
None.
- is cloned from
-
JRACLOUD-89221 Increase the issue limit in Advanced Roadmap Plans
- Waiting for Release
- is related to
-
JPOSERVER-2918 Increase the project, issue, and team limits in Plan
- Closed
-
JSWSERVER-24771 Increase the project, issue, and team limits in Plan
- Gathering Interest
-
ENT-2268 Loading...
-
ACE-9760 Loading...
- relates to
-
JRACLOUD-92476 Add issue limit warning when configuring issue source
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...