• 166
    • 62
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Update - September 2024

      Hi everyone,

      Thank you for taking the time to share your feature request with us. Your input is greatly appreciated, and we understand the effort and dedication it takes to provide us with your thoughts and ideas.

      We are actively looking into a solution for this feature request. Our team is committed to thoroughly investigating the best way to address this need, and we will keep you informed if we get closer to a possible release date.

      Thank you to every person who provided feedback on this issue. We will update you as soon as we have more concrete information to share. 

      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.

            [JRACLOUD-89221] Increase the project and issue limit in Advanced Roadmap Plans

            Yi Meng added a comment -

            Jira plan (a.k.a advanced roadmap) looks good when I introduce it to senior management team for organizational cross-projects planning. But the soft limit of 5000 issues will make it hard for the organization to use it in planning with confidence. In the real world, the limits is easy to be broken considering the number of ongoing work items across teams/projects. This request should be assigned with highest priority to solve. We're on Jira Cloud premium plan and it allows us to have unlimited projects. If there is such a small limits for plan, it will limit the usage of plan and it will become something which looks beautiful but useless. 

            Yi Meng added a comment - Jira plan (a.k.a advanced roadmap) looks good when I introduce it to senior management team for organizational cross-projects planning. But the soft limit of 5000 issues will make it hard for the organization to use it in planning with confidence. In the real world, the limits is easy to be broken considering the number of ongoing work items across teams/projects. This request should be assigned with highest priority to solve. We're on Jira Cloud premium plan and it allows us to have unlimited projects. If there is such a small limits for plan, it will limit the usage of plan and it will become something which looks beautiful but useless. 

            Hey all, 

            Adding some votes for this. We have sold the dream of managing large portfolios of work in Plans, but we are getting limited by this. Like everyone else in the world, we don't want to use Align to manage this, we want it in Plans. 

            Any updates on this? 

            Thanks,
            Steve

            Steven Drury added a comment - Hey all,  Adding some votes for this. We have sold the dream of managing large portfolios of work in Plans, but we are getting limited by this. Like everyone else in the world, we don't want to use Align to manage this, we want it in Plans.  Any updates on this?  Thanks, Steve

            We were able to convince one customer that Jira in combination with Plans is a good way to map formalized project management according to a project management manual.
            On the other hand, we created a way for management and product owners to get an overview of the portfolio and the dependencies between projects down to work package level.
            With the limitation to 100 Jira projects, this is not possible in this group. 
            Can a solution be expected in the foreseeable future?
            Or should I advise the customer to opt for a Big Picture solution?

            Marc Nerenberg added a comment - We were able to convince one customer that Jira in combination with Plans is a good way to map formalized project management according to a project management manual. On the other hand, we created a way for management and product owners to get an overview of the portfolio and the dependencies between projects down to work package level. With the limitation to 100 Jira projects, this is not possible in this group.  Can a solution be expected in the foreseeable future? Or should I advise the customer to opt for a Big Picture solution?

            We are now up to 22 teams and this limit is even more of an issue.  Please consider raising the priority on this.

            keith.vorderbruggen added a comment - We are now up to 22 teams and this limit is even more of an issue.  Please consider raising the priority on this.

            Nevo Alva added a comment -

            We are struggling with this limit for 2 years now, it practically makes the entire feature unusable for us and we spend so much wasted time on workarounds. the goal of a good project management tool is to save time and not create these barriers and waste. 

            Nevo Alva added a comment - We are struggling with this limit for 2 years now, it practically makes the entire feature unusable for us and we spend so much wasted time on workarounds. the goal of a good project management tool is to save time and not create these barriers and waste. 

            Surprised that there hasn't been an update in this since 2016!  This would definitely be helpful for mid to large sized companies.  

            Gemma, John P added a comment - Surprised that there hasn't been an update in this since 2016!  This would definitely be helpful for mid to large sized companies.  

            Agree with Mark Dunlap and prior comments.  We have ALOT of cross-project dependencies and as such need to pull in the scope of multiple projects into our Plans causing us to constantly exceed the limit.  Expansion would go a long way.

            ⬇⬇⬇❤❤❤❤❤❤❤❤⬇⬇⬇ 

            Jackson, Keith W added a comment - Agree with Mark Dunlap and prior comments.  We have ALOT of cross-project dependencies and as such need to pull in the scope of multiple projects into our Plans causing us to constantly exceed the limit.  Expansion would go a long way. ⬇⬇⬇❤❤❤❤❤❤❤❤⬇⬇⬇ 

            Bumping this.  There are many realistic use cases which would require >5,000 issues in a single plan.  There should be simple ways of engineering this on Cloud to allow a more liberal cap.  On behalf of other large enterprise customers, please prioritize this to help Plans realize its full potential!

            Dunlap, Mark J added a comment - Bumping this.  There are many realistic use cases which would require >5,000 issues in a single plan.  There should be simple ways of engineering this on Cloud to allow a more liberal cap.  On behalf of other large enterprise customers, please prioritize this to help Plans realize its full potential!

            Our SLT is using an Advanced Roadmap to see where we are in our Chief Data Office.  We have 15 teams and go well beyond the 5,000 Issue limit.  Please increase this to at least 20,000, but unlimited would be best.  

            keith.vorderbruggen added a comment - Our SLT is using an Advanced Roadmap to see where we are in our Chief Data Office.  We have 15 teams and go well beyond the 5,000 Issue limit.  Please increase this to at least 20,000, but unlimited would be best.  

            remove the limit please!! we need 15000++ issues and 200++ projects in the plan 

            Lars-Harald Båtnes added a comment - remove the limit please!! we need 15000++ issues and 200++ projects in the plan 

              a0c6d525c56b Mohamed Almoaz
              vkharisma vkharisma
              Votes:
              232 Vote for this issue
              Watchers:
              124 Start watching this issue

                Created:
                Updated: