Well another workaround is to identify all the source lists, then include them in the search for your tasks (by using the locations attribute each task) to identify e.g. your task is on your sprint of interest. Then also check the sprints because there may be cards added to them. Combine all and you should have the total set. Unless someone adds from another list you didn't know about. Slow and cumbersome but will work.

Agree - this is completely unusable and took me a while to figure out what was happening. Should be able to get the list of tasks in any list (even if they originate in other lists).

We also really need this feature ASAP.

As a workaround it is possible to use views and GetViewTasks. Which feels very hacky, because it will return only the visible tasks on the view. So when someone activates a filter, GetViewTasks will return less/more tasks.

The workaround to that is using the API to create a private view which displays all tasks of the list.

We run our sprints using secondary lists that is fed from the main backlog lists. Because this feature is not available I have to manually run a file on the beginning and end of each sprint. If this were available I could automate that capture.

The API also feeds our customer success tool so that the customer requested work can be visible to the POC. They will be able to see the tasks but they cannot see at a glance if they in the current sprint.

This is becoming a bigger issue for us. You can't get items added to a sprint because of this issue. A huge problem.

We have many workflows that depend on tasks living in a primary list but then being added to additional lists, where we still need to be able to get ALL the tasks in a list, even if their Home list is different.

Zach is this anything the team is planning to fix with the API? It's bothered me for a while, but now it's becoming a blocker. Is it really something that would require an overhaul just to allow us to get the tasks in a list, even if some of the tasks have a different home list?

This is such a bizarre shortcoming for the API and makes Clickup almost unusable if you can't trust it to return all tasks in a view or for a list just because tasks are part of multiple lists. It seems inconsistent as some tasks in multiple lists are returned.

We use lists for sprints and keep old sprint list links around so we can track tasks that are stuck and span several sprints without completing. Instead of being able to do that, we are blind to this work from an API perspective.

Can someone reply with an ETA (if ever) for this fix? If there isn't one, I'm probably going to recommend that we move to Jira or some other tool that can give us full visibility to tasks.

Beyond the API, Many of the dashboard widgets don't support multiple lists either so we really have poor visibility around most of our work. Please fix this as I see promise in this software if we can!

Even if I can change our processes to only try to have tasks on one list, it's too easy for a task to be added to a second list and then we'd be blind to that task in several dashboard widgets and the API (unless there is a "strict mode" we can use to prevent tasks from being part of multiple lists.

I see https://clickup.com/api/clickupreference/operation/AddTaskToList/ in the api docs now

It would be great if you could at least explain your reasoning behind not exposing this basic and simple functionality.

Really nuts, that they do not have it

This is so stupid that they don't have it