List view - 'Select All' from list settings or from grouped header does not select all
A
Alan Ballany
When in list view, if I select 'Select All' from the list settings header, or from 'grouped by' header, not all tasks are selected, the selection stops part way through the list of tasks
Log In
Luci N.
open
Hey, everyone! Thank you for following along on this post and providing your feedback!
To keep everyone informed, we've updated the status of this Canny post to reflect current product initiatives.
This request is still very much on our radar and the ClickUp team will keep this post up to date when we have more to share regarding this feature in the future!
Pierre Becher
Brent Evans when will this be fixed? It's open since 2019... A "Select all" button means I want to select all tasks, like ALL tasks in that list and not only those tasks which are visible/loaded in the frontend. I had to scroll down like 5 minutes to select all of the tasks in the list. How should people with lots of data/tasks work like this?
Shaquille Payne
Merged in a post:
Select all tasks requires loading them first
Janis Billepp
When I have a huge list of tasks I need to scroll down and load them every time in order to bulk edit, since select all only lets me select the loaded ones.
It would be great to be able to select ALL tasks (even the ones not visible at the loaded page) to not having to scroll all the way down (which takes along time due to buffering - scrolling - buffering - scrolling ...)
T
Tom Proudman
This is a major bug for us, as we often have to make updates to multiple tasks at the same time. Each of our lists will typically contain hundreds of tasks and subtasks. The problem is compounded when trying to make updates to multiple tasks across multiple lists/locations. Currently the workaround involves scrolling to the bottom extent of the list, so that every task in the list is rendered in the browser page. As you scroll through each set of 30-40 tasks you have to wait a few seconds for the lazy load to render the next set of 30-40 tasks. Having eventually (this can take several minutes!) reached the bottom of the list, it is then necessary to scroll all the way up again to access the 'select all' feature (which disappears from view when scrolling). I would really appreciate an update on when this is likely to be resolved. I'm surprised there aren't more votes for this. I suspect there may be several other bug tickets that pertain to the same bug and may have more votes. Thanks.
Pierre Becher
Tom Proudman: agreed, it's hardly usable like this.
Florian Schardt
I have the same problem. Total I have 102 tasks and subtasks. I need to scroll down and wait for the tasks to be shown one after the other. Only after that I can scroll up again and use the "Select all" function. Little anoying!
John R Crowley Jr
Right! So weird, select all, is not select all, it is select some.
Include the option to select all subtasks too.
Nicolas Houdeville
Hi! I do agree that this is a problem for me. You guys are doing great work but it then lead the user to rethink about the way ClickUp is used (which is great btw). For example, with the birth of automation I expect to transform one of my folder in ClickUp into a Ticketing system. For this I need to select all tasks in a list to apply some custom fields change and even on closed tasks. Which means sometime 300 of them, and believe me, it is a pain in the ass to select only part of them at a time. I'm sure you will solve this... I hope...
Brent Evans
under review
Brent Evans
Hey everyone!
Thanks for reaching out about this! We're using lazy loading for tasks that are not yet rendered on the screen, which is why 'select all' only applies to tasks that are already loaded. We certainly agree that this is an issue and intend to fix this in the future, but it's just a tricky issue that requires too much development work for us to resolve at this time.
Apologies for the trouble here! We'll make sure to reach out as soon as this changes 😊
Brianne Davis
This option now seems to be missing entirely from the "grouped by" header, which is very frustrating because I use that all the time
Brianne Davis
It looks like the option was just moved, but because of the move it is no longer available if the tasks are ungrouped
Load More
→