• 1,163
    • 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.

      Update - June 20th, 2024

      Hi everyone, as promised in the last update, we have now also shipped the new experience for team-managed projects.
      Team-managed Jira boards with more than 5,000 issues will now display the first 5,000 issues based on the board filter settings.
      You can read more about issue limits in team-managed projects here.

      With this final update, we are now closing this ticket and would like to thank everyone for their patience and for sharing invaluable feedback with us.
      You can still continue sharing your thoughts and feedback about the new experience with us through community.

      Best,
      Megha Chaudhry
      Principal Service Enablement Engineer - Jira Cloud


      Update - June 3rd, 2024

      Hi everyone, this is Megha from the Jira team. I’m pleased to share that we have updated our board and backlog experience for company-managed projects.
      A Jira board that contains more than 5,000 issues will now display the first 5,000 issues based on the board filter settings.

      Read more about how this feature works in my community post.
      At the moment, this update is only for company-managed projects. But we’ll be rolling it out to team-managed projects as well in the coming weeks.
      We thank you for your patience as we work through these changes.

      Best,
      Megha Chaudhry
      Principal Service Enablement Engineer - Jira Cloud


      Problem Statement

      Filter Query with more that 5000 issues displays "Too many issues are trying to load":

      Suggestion

      Allow more that 5000 issues to be displayed on the board

      Notes

      Per release notes in December 2017:
      https://confluence.atlassian.com/cloud/blog/2017/12/atlassian-cloud-changes-dec-11-to-dec-18-2017#AtlassianCloudchangesDec11toDec18,2017-jira.software

      Boards display a maximum of 5000 issues
      To reduce slow load times and accelerate your Jira experience, boards will now display a maximum of 5000 issues at a time. If your board tries to display more than 5000 issues, you'll be prompted to update your filters.

      Workaround

      Company-managed

      The currently available workaround would be to create more than one board within the same project, splitting the current unique board and applying to each new board different filters on Board Settings > General.

      For example, for one board you may have only issues of a specific issue type or which contains a specific label.

      Of course, this will depend on your process, so you would need to check which field value/specific details of issues could be used to create separate queries.

          Form Name

            [JRACLOUD-85646] Allow Query Result to be able to view > 5000 issues

            Pinned comments

            Pinned by Megha

            Megha added a comment -
            Update - June 3rd, 2024

            Hi everyone, this is Megha from the Jira team. I’m pleased to share that we have updated our board and backlog experience for company-managed projects.
            A Jira board that contains more than 5,000 issues will now display the first 5,000 issues based on the board filter settings.

            Read more about how this feature works in my community post.
            At the moment, this update is only for company-managed projects. But we’ll be rolling it out to team-managed projects as well in the coming weeks.
            We thank you for your patience as we work through these changes.

            Best,
            Megha Chaudhry
            Principal Service Enablement Engineer - Jira Cloud

            Megha added a comment - Update - June 3rd, 2024 Hi everyone, this is Megha from the Jira team. I’m pleased to share that we have updated our board and backlog experience for company-managed projects. A Jira board that contains more than 5,000 issues will now display the first 5,000 issues based on the board filter settings. Read more about how this feature works in my community post . At the moment, this update is only for company-managed projects. But we’ll be rolling it out to team-managed projects as well in the coming weeks. We thank you for your patience as we work through these changes. Best, Megha Chaudhry Principal Service Enablement Engineer - Jira Cloud

            Pinned by Megha

            Megha added a comment -
            Update - June 20th, 2024

            Hi everyone, as promised in the last update, we have now also shipped the new experience for team-managed projects.
            Team-managed Jira boards with more than 5,000 issues will now display the first 5,000 issues based on the board filter settings.
            You can read more about issue limits in team-managed projects here.

            With this final update, we are now closing this ticket and would like to thank everyone for their patience and for sharing invaluable feedback with us.
            You can still continue sharing your thoughts and feedback about the new experience with us through community.

            Best,
            Megha Chaudhry
            Principal Service Enablement Engineer - Jira Cloud

            Megha added a comment - Update - June 20th, 2024 Hi everyone, as promised in the last update, we have now also shipped the new experience for team-managed projects. Team-managed Jira boards with more than 5,000 issues will now display the first 5,000 issues based on the board filter settings. You can read more about issue limits in team-managed projects here . With this final update, we are now closing this ticket and would like to thank everyone for their patience and for sharing invaluable feedback with us. You can still continue sharing your thoughts and feedback about the new experience with us through community. Best, Megha Chaudhry Principal Service Enablement Engineer - Jira Cloud

            All comments

            Pinned by Megha

            Megha added a comment -
            Update - June 20th, 2024

            Hi everyone, as promised in the last update, we have now also shipped the new experience for team-managed projects.
            Team-managed Jira boards with more than 5,000 issues will now display the first 5,000 issues based on the board filter settings.
            You can read more about issue limits in team-managed projects here.

            With this final update, we are now closing this ticket and would like to thank everyone for their patience and for sharing invaluable feedback with us.
            You can still continue sharing your thoughts and feedback about the new experience with us through community.

            Best,
            Megha Chaudhry
            Principal Service Enablement Engineer - Jira Cloud

            Megha added a comment - Update - June 20th, 2024 Hi everyone, as promised in the last update, we have now also shipped the new experience for team-managed projects. Team-managed Jira boards with more than 5,000 issues will now display the first 5,000 issues based on the board filter settings. You can read more about issue limits in team-managed projects here . With this final update, we are now closing this ticket and would like to thank everyone for their patience and for sharing invaluable feedback with us. You can still continue sharing your thoughts and feedback about the new experience with us through community. Best, Megha Chaudhry Principal Service Enablement Engineer - Jira Cloud

            mchaudhry Thank you SO MUCH for this. 

            All the folks reading these threads must see how vocal I have been.

            The lesson here is that persistence and respect go a long way toward healthy communication. While Atlassian has appeared very unreceptive to many of us, it is not entirely intentional. We post a lot of requests and comments on the boards and in the project. Sometimes follow-up is required.

            I've seen MANY people say that reaching out is ineffective, that Atlassian doesn't listen.

            This is a great example of how they do listen, when we give them opportunity and incentive. Never feel like your voice is too small. Never allow yourself to feel helpless, and great things can be done.

            This is one of four large issues we were having, and Atlassian really came through for us, once we gave them the opportunity to be aware of our issues.

            I'd like to thank Atlassian for making great effort this year to reconnect with their customer base. It's been wonderful!

            William Wilson added a comment - mchaudhry Thank you SO MUCH for this.  All the folks reading these threads must see how vocal I have been. The lesson here is that persistence and respect go a long way toward healthy communication. While Atlassian has appeared very unreceptive to many of us, it is not entirely intentional. We post a lot of requests and comments on the boards and in the project. Sometimes follow-up is required. I've seen MANY people say that reaching out is ineffective, that Atlassian doesn't listen. This is a great example of how they do listen, when we give them opportunity and incentive. Never feel like your voice is too small. Never allow yourself to feel helpless, and great things can be done. This is one of four large issues we were having, and Atlassian really came through for us, once we gave them the opportunity to be aware of our issues. I'd like to thank Atlassian for making great effort this year to reconnect with their customer base. It's been wonderful!

            Pinned by Megha

            Megha added a comment -
            Update - June 3rd, 2024

            Hi everyone, this is Megha from the Jira team. I’m pleased to share that we have updated our board and backlog experience for company-managed projects.
            A Jira board that contains more than 5,000 issues will now display the first 5,000 issues based on the board filter settings.

            Read more about how this feature works in my community post.
            At the moment, this update is only for company-managed projects. But we’ll be rolling it out to team-managed projects as well in the coming weeks.
            We thank you for your patience as we work through these changes.

            Best,
            Megha Chaudhry
            Principal Service Enablement Engineer - Jira Cloud

            Megha added a comment - Update - June 3rd, 2024 Hi everyone, this is Megha from the Jira team. I’m pleased to share that we have updated our board and backlog experience for company-managed projects. A Jira board that contains more than 5,000 issues will now display the first 5,000 issues based on the board filter settings. Read more about how this feature works in my community post . At the moment, this update is only for company-managed projects. But we’ll be rolling it out to team-managed projects as well in the coming weeks. We thank you for your patience as we work through these changes. Best, Megha Chaudhry Principal Service Enablement Engineer - Jira Cloud

            It should be possible to increase the amount of issues shown in a board, 5000 is not enough. Especially since "Closed" issues are included in the 5000 issues.

            Fabian Gugler added a comment - It should be possible to increase the amount of issues shown in a board, 5000 is not enough. Especially since "Closed" issues are included in the 5000 issues.

            Another MUST that is treated lightly by the development/performance department of Atlassian. I wonder if they have certain employees who INSPECT or create cases of new features or improve and recommend new ones. In the end, as with many others, this feature will be part of an add-on/plugin - and Atlassian would say: "Don't get me wrong...we will...bla bla..." => pure sales, marketing, whatever. 

            l.seplecan added a comment - Another MUST that is treated lightly by the development/performance department of Atlassian. I wonder if they have certain employees who INSPECT or create cases of new features or improve and recommend new ones. In the end, as with many others, this feature will be part of an add-on/plugin - and Atlassian would say: "Don't get me wrong...we will...bla bla..." => pure sales, marketing, whatever. 

            This is insane. We need at least the double amount of issues in a plan, this because we need to coordinate work between project plans and people across the entire company. 5000 issues isn't enough even to make the boilerplate structure for all our projects. It impossible for us to coordinate work in respect of team capacity and projects plan as the limit sits now. Please update!!!

            Lars-Harald Båtnes added a comment - This is insane. We need at least the double amount of issues in a plan, this because we need to coordinate work between project plans and people across the entire company. 5000 issues isn't enough even to make the boilerplate structure for all our projects. It impossible for us to coordinate work in respect of team capacity and projects plan as the limit sits now. Please update!!!

            William Wilson added a comment - - edited

            How many votes need to exist here before this gets done? This is utter insanity. You KNOW there are plenty of people... ie: EVERYONE that has migrated to cloud, that wants this. And you've put out many statements about the improved cloud performance. So it makes no sense that you are not addressing an issue so fundamental, nor are you communicating about any plans for it. 

            So, allow me to communicate clearly in your absence. We are a 6 figure customer of yours, and because of the recent direction you've taken, the moment I can justify the expense of moving away from Atlassian, I will be advocating the move, unless things change between now and then. This is a MONUMENTAL issue that needs to be taken care of, and you don't even have the common decency to communicate any intent or timeline. 

            William Wilson added a comment - - edited How many votes need to exist here before this gets done? This is utter insanity. You KNOW there are plenty of people... ie: EVERYONE that has migrated to cloud, that wants this. And you've put out many statements about the improved cloud performance. So it makes no sense that you are not addressing an issue so fundamental, nor are you communicating about any plans for it.  So, allow me to communicate clearly in your absence . We are a 6 figure customer of yours, and because of the recent direction you've taken, the moment I can justify the expense of moving away from Atlassian, I will be advocating the move, unless things change between now and then. This is a MONUMENTAL issue that needs to be taken care of, and you don't even have the common decency to communicate any intent or timeline. 

            You know... the thought just occurred to me.

            Maybe the reason this is not getting done... is because they can't display more than 5000 issues on THEIR backlog! Can't display them, they don't exist, right?

            Logic.

            William Wilson added a comment - You know... the thought just occurred to me. Maybe the reason this is not getting done... is because they can't display more than 5000 issues on THEIR backlog! Can't display them, they don't exist, right? Logic.

            Yet another core feature critical to many of us, removed. What shocks me is that there is no "Buy this add-on to solve this problem". That's a first!

            Every single day, we lose functionality, to have it replaced with something non-essential.

            • We have a NEW WAY to create tickets... I mean, the old way wasn't broken. But we have a new way. This was CLEARLY a priority over things that disrupt functionality!
            • We have a new "TEAM" custom field we can enable. Of course, you could have just created a TEAM custom field... but hey... it was far more important to dedicate person-hours to that custom field, than it is to dedicate those hours to something... you know... important. Like being able to view all my issues in the backlog. Because, who has more than 5,000 issues in a company doing development work?

            Oh...  and my favorite part of all this...

            We can't display more than 5000 entries (is this 1982?) because of "performance issues"...

            BUT


            Atlassian Cloud changes Sep 25 to Oct 2, 2023

            Searching for issues just got faster in Jira Cloud

            ROLLING OUT

            We’ve modernized, optimized, and redesigned the way you search for issues. With features like smart syntax highlighting and enhanced autocomplete, the new JQL editor lets you build powerful queries for accurate search results. Configure and reorder columns to see what’s most important to you. Learn more about the new issue search in Jira Cloud


             

            So... Atlassian has, several times over, informed us that they've improved their search and JQL performance... but being able to view 5001 issues from their cloud offering in Q4 2023 still takes too long? So... Atlassian... what you are saying is... you have "modernized, optimized, and redesigned the way we search for issues". But you have not "modernized, optimized, and redesigned the performance of issue searches."

            NO ASSIGNEEE... NO ROADMAP... NO TIMELINE... JUST EXCUSES. 

            And I don't even understand WHY. (I do. It has to do with bad choices (tm))

            I IMPLORE Atlassian to begin dedicating hours to these problems.

            Short of that, I would also suggest that people start letting Atlassian know that this is not acceptable. Start migrating those things that you easily can, away from Atlassian, and exercise your spending power to remind Atlassian what is important to us. Little things like choosing not to renew a marketplace add-on through Atlassian with some documentation in your decision, go a long way.

            "They don't care what we have to say. They care about how much we're willing to pay!"

            Show them that we're not going to continue paying premium fees for a product that keeps outsourcing it's functionality!

            And if you can't do that, then join me in being vocal. They know that very few of us can do a 180 and just change direction after we've invested a quarter of a million dollars or more into migrating to their cloud. Or afford the same cost in migrating to a new tool. But they have to know that more and more of us will... at the first opportunity, if Atlassian doesn't start altering course to be more observant of our requests.

            I am constantly evaluating new products. And every single time we run into an issue, my suggestion to my coworkers is that we set up a POC to see if it will serve us. 3 years ago, it was more trouble for my users to think about something new. Now? It's more trouble for my users to try to find fixes and workarounds. For every problem we've had in Jira or Confluence since our migration, we've found a less expensive third party solution NOT associated with Atlassian.

            We're beginning to build out solutions with partners that "play well together" and remain focused on priorities more aligned with my organization's technical and financial requirements. Little by little. Piece by piece. 

            I'm not trying to be a jerk. I'm saying all of this because I like Atlassian's legacy products. I like the ideas and promises they make. And I want to remain an Atlassian customer. But this is not MY choice! This is Atlassian out-pricing themselves and not keeping critical functionality in the product(s). I mean, you can't even remove the borders from a table in their wiki product UNLESS YOU BUY AN ADD-ON anymore!

            William Wilson added a comment - Yet another core feature critical to many of us, removed. What shocks me is that there is no "Buy this add-on to solve this problem". That's a first! Every single day, we lose functionality, to have it replaced with something non-essential. We have a NEW WAY to create tickets... I mean, the old way wasn't broken. But we have a new way. This was CLEARLY a priority over things that disrupt functionality! We have a new "TEAM" custom field we can enable. Of course, you could have just created a TEAM custom field... but hey... it was far more important to dedicate person-hours to that custom field, than it is to dedicate those hours to something... you know... important. Like being able to view all my issues in the backlog. Because, who has more than 5,000 issues in a company doing development work? Oh...  and my favorite part of all this... We can't display more than 5000 entries (is this 1982?) because of "performance issues"... BUT Atlassian Cloud changes Sep 25 to Oct 2, 2023 Searching for issues just got faster in Jira Cloud ROLLING OUT We’ve modernized, optimized, and redesigned the way you search for issues. With features like smart syntax highlighting and enhanced autocomplete, the new JQL editor lets you build powerful queries for accurate search results. Configure and reorder columns to see what’s most important to you.  Learn more about the new issue search in Jira Cloud   So... Atlassian has, several times over, informed us that they've improved their search and JQL performance ... but being able to view 5001 issues from their cloud offering in Q4 2023 still takes too long? So... Atlassian... what you are saying is... you have "modernized, optimized, and redesigned the way we search for issues ". But you have not "modernized, optimized, and redesigned the performance of issue searches. " NO ASSIGNEEE... NO ROADMAP... NO TIMELINE... JUST EXCUSES.  And I don't even understand WHY. (I do. It has to do with bad choices (tm)) I IMPLORE Atlassian to begin dedicating hours to these problems. Short of that, I would also suggest that people start letting Atlassian know that this is not acceptable. Start migrating those things that you easily can, away from Atlassian, and exercise your spending power to remind Atlassian what is important to us. Little things like choosing not to renew a marketplace add-on through Atlassian with some documentation in your decision, go a long way. "They don't care what we have to say. They care about how much we're willing to pay!" Show them that we're not going to continue paying premium fees for a product that keeps outsourcing it's functionality! And if you can't do that, then join me in being vocal. They know that very few of us can do a 180 and just change direction after we've invested a quarter of a million dollars or more into migrating to their cloud. Or afford the same cost in migrating to a new tool. But they have to know that more and more of us will... at the first opportunity, if Atlassian doesn't start altering course to be more observant of our requests. I am constantly evaluating new products. And every single time we run into an issue, my suggestion to my coworkers is that we set up a POC to see if it will serve us. 3 years ago, it was more trouble for my users to think about something new. Now? It's more trouble for my users to try to find fixes and workarounds. For every problem we've had in Jira or Confluence since our migration, we've found a less expensive third party solution NOT associated with Atlassian. We're beginning to build out solutions with partners that "play well together" and remain focused on priorities more aligned with my organization's technical and financial requirements. Little by little. Piece by piece.  I'm not trying to be a jerk. I'm saying all of this because I like Atlassian's legacy products. I like the ideas and promises they make. And I want to remain an Atlassian customer. But this is not MY choice! This is Atlassian out-pricing themselves and not keeping critical functionality in the product(s). I mean, you can't even remove the borders from a table in their wiki product UNLESS YOU BUY AN ADD-ON anymore!

            Stephanie added a comment - - edited

            When is this feature going to be implemented and released?
            I have a project where I already have 5400 issues and it is just the middle of the project, most tasks are connected to each other and I can't move some of them to another project to filter issues properly
            Also, I have Tempo plugin and 2 projects will not work for it afaIk

            Stephanie added a comment - - edited When is this feature going to be implemented and released? I have a project where I already have 5400 issues and it is just the middle of the project, most tasks are connected to each other and I can't move some of them to another project to filter issues properly Also, I have Tempo plugin and 2 projects will not work for it afaIk

              mchaudhry Megha
              ashohaimi Syauqi (Inactive)
              Votes:
              201 Vote for this issue
              Watchers:
              170 Start watching this issue

                Created:
                Updated:
                Resolved: