Tasks in multiple list are not available via Clickup API
Alex Mauzon
Tasks in multiple list are not available via Clickup API.
Log In
Canny AI
Merged in a post:
API - Tasks/Sub Tasks identified in multiple lists
B
Brad Hawkins
I use Sunsama as a Daily/Weekly planner. Currently, if I have tasks/sub tasks in multiple lists, Sunsama cannot see the task/sub task.
Sunsama can "look" at individual lists of tasks/sub tasks and also folders and "everything". Whilst that's great, I often don't want to see all the "noise" (every single task) so I would prefer to only see a handful of tasks that I want/are ready to schedule. Initially I thought that a "To Be Scheduled" list would work. And it does, to some degree, but isn't ideal. Let me explain further.
So, for example (and in my use case):
"Project A" lives in the "Service Projects" list and I would prefer it stays there for the duration of its lifespan (until archived). I think that makes sense for most use cases.
Then, within "Project A" one is very likely to have "tasks" and possibly "sub tasks" related to "Project A". I have the "Business Plus" ClickUp plan so I can have both tasks and sub tasks in separate lists. That works great if I need to see them elsewhere, however, if I keep "Project A" in the "Service Projects" list but I ADD several tasks and/or sub tasks to the "To Be Scheduled" list, Sunsama cannot "see" them in that list BECAUSE the parent task "Project A" lives in a separate list so the tasks and sub tasks are also related to that list.
There only seems to be two ways to "see" them in that list. Either I drag and drop the task or sub task out of "Project A" and into the "To Be Scheduled" list (and it completely loses it's association with "Project A", so not the best move), OR, I have to completely MOVE "Project A" and ALL of the associated tasks and sub tasks to the "To Be Scheduled" list. Also not overly desirable as I might only want to work on/schedule some of the tasks and/or sub tasks AND I don't want to see the parent task ("Project A") in that list. That also gets messy and is simply too much work with all the projects I have in progress.
Can you alter the API so Sunsama can work with tasks and sub tasks across multiple lists?
According to Sunsama, the issue is currently a limitation with the ClickUp API.
Thanks.
Tyson Clegg
This is a big issue for us as well. I spent a decent amount of time building out an integration, only to get blocked by this at the last mile. This seems like basic functionality, and its unfortunate to see people still experiencing this same issue almost 5 years after the thread was started.
S
Shelby
I just figured out this was the reason my API calls aren't returning any tasks! This is a huge drag. I'm going to try to work around by calling the API to update a view to filter on tasks with that list location, then separately get tasks in the (revised filtered) view, but this could be a challenge and introduce more error points.
Travis Austin
Really disapponted that this isn't added. Makes compiling Sprint data for capacity planning basically impossible! How do I get this data??
S
Shaun Bruno
Have to echo the other commentators - this is an essential feature and should be readily prioritized.
Consider the following scenario as a base case:
- All tickets Home is "Backlog"
- Ticket is placed in Sprint List
- Get Task API request to Sprint List is missing tickets because they all "live" in Backlog.
Donnchadh O h-Ainle
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.
Donnchadh O h-Ainle
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).
Stefan Lamp
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.
Cliff Phillips
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.
A
Andrew Wilkins
This is a huge shortcoming for us
Load More
→