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.
Log In
A
Andrew Wilkins
This is a huge shortcoming for us
S
Sean Cofoid
This is an issue with the API only exposing the "home" list of a (sub)task. This makes Power BI reporting on sprints impossible, since the desired way to create (sub)tasks is to create them in a project folder to keep all related items together, then assign tasks to a sprint list at the start of a sprint. This means that none of the (sub)tasks in a sprint will ever have their home folder in a sprint, which makes it impossible to do sprint reporting.
A possible solution would be to add a GET TASKS method to the API that returned a list of tasks with an array of the lists a task is associated with. This would functionally reverse the order of operations for populating data from the API. Alternately, the GET LIST method could return an array for each list that includes all the tasks associated with that list, regardless of whether the list is the "home" list.