Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-91580

Increase Issues/Epic limit for Jira Next-gen / Team-Managed roadmap

    • 9
    • 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.

      Problem Statement

      As per the following documentation: Enable the roadmap, the Next-gen Roadmap can display a maximum of 3000 issues or 300 Epics at the moment, and after that limit the functionality will not longer work.

      Suggestions:

      • Provide the ability to increase the number of Issues/Epics that can be displayed on the Roadmaps.
      • Display a warning when the limit is about to be reached.

      Workarounds:

      • Mark Epics as Done and/or backdate the due date, e.g to more than one year ago.
      • Move old issues to other projects

       

            [JRACLOUD-91580] Increase Issues/Epic limit for Jira Next-gen / Team-Managed roadmap

            Closing as duplicate ticket - Issue limit has been increased to 5000 on the roadmap.

            Rathesh Richards (Inactive) added a comment - Closing as duplicate ticket - Issue limit has been increased to 5000 on the roadmap.

            We have a studio of less than 20 people and of course we've hit over 3000 issues as it's a multiyear project. Can we please support a workaround for this or tell the Roadmap to ignore closed/resolved issues? I have less than 3000 OPEN issues, and less than 300 Epics, but we still have this message. 

            Michael Kelly added a comment - We have a studio of less than 20 people and of course we've hit over 3000 issues as it's a multiyear project. Can we please support a workaround for this or tell the Roadmap to ignore closed/resolved issues? I have less than 3000 OPEN issues, and less than 300 Epics, but we still have this message. 

            Same here, it spoils an otherwise great feature, why can't it page 300 items at a time and /or we have a configuration option to decide the maximum?

            Andrew.Munt added a comment - Same here, it spoils an otherwise great feature, why can't it page 300 items at a time and /or we have a configuration option to decide the maximum?

            We will find this functionality extremely useful too. We're currently sitting with more than 300 epics and are unable to use the road map feature even though we desperately want to.

            Gideon Nieuwoudt added a comment - We will find this functionality extremely useful too. We're currently sitting with more than 300 epics and are unable to use the road map feature even though we desperately want to.

            Increasing this limit would be extremely useful. We rely on the Roadmap for resource planning a team of 10 developers, hence the large number of issues within the past year.

            We have hit our limit, and have been blocked from carrying our our regular processes, with no warning or way to resolve this without deleting issues in the project. The latter solution does not work as it would delete the log of work carried out which would have downstream impacts.

            Prior to reaching the limit, the performance of the roadmap was adequate with the max number of issues.

            Bradley Wilton added a comment - Increasing this limit would be extremely useful. We rely on the Roadmap for resource planning a team of 10 developers, hence the large number of issues within the past year. We have hit our limit, and have been blocked from carrying our our regular processes, with no warning or way to resolve this without deleting issues in the project. The latter solution does not work as it would delete the log of work carried out which would have downstream impacts. Prior to reaching the limit, the performance of the roadmap was adequate with the max number of issues.

              762b441b532a Rathesh Richards (Inactive)
              b678926ca497 Bopanna
              Votes:
              26 Vote for this issue
              Watchers:
              24 Start watching this issue

                Created:
                Updated:
                Resolved: