Custom Fields Not returns with include subtasks is set to true
not on the roadmap
S
Scott J Nichols
I group all information for a project within a Primary Project Task, and group sub tasks as specific types of categories for the project.
For instance, a Project will always have a single sub task assigned as an Appointment. A Project will always contain 1 or more TimeLogs. A time log category is a subtask, and all time log entries are contained as sub tasks to the Time Log Category.
A Project may have 1 or more Financial Transactions such as deposits, and expenditures. These are all contained with the Transactions sub task for the Project.
The Project Task Record contains a set of custom fields specific to each Project Category, time logs, transactions, appointment, photo gallery, documents, etc. I have a set of custom fields for TimeLog, StartTime, EndTime, hours, laborers. If there is more than a single laborer, the time log task contains a set of sub tasks to identify laborers for the that time log. If the laborer's start and/or end times are different another sub task is created to maintain that information.
So for at Project, a time log category is created and 1:M sub tasks for the time log category are created for each time log entry. A time log sub task entry may have more than a single laborer for that time log. Each Laborer is a sub task to the time log entry. If the laborer has a different set of times which is different than the time log, but on the same date, that information is specific to that laborer and is stored on the task for that laborer.
So when I go to access all the information for a project, and the include_subtasks=true, not having the custom fields available for each sub task that means I have to recursively loop through each sub task to acquire the set of custom fields for that sub task.
Recursive loops (calling the same function within an array tree) is practically impossible with api call because by their very nature are linear and don't lend themselves available to call the same function in a recursive nature.
Presently I have to use a separate api call to get the custom fields for each of the sub tasks. It would be great to have an option to include_custom_fields.
Thanks, Scott.
Log In
Autopilot
Merged in a post:
Return Subtask Metadata in Task API
B
Bryan Girkins
When using a parent taskId with 'include_subtasks=true', the GET Task API does not return complete data for the subtasks associated with the parent task.
Most notably, the 'custom_fields' data is NULL. That is very frustrating and defeats the purpose. I might as well just feed all taskId values into their own calls instead of saving time using the parent taskId.
Further, I noticed other fields are also missing. When using a basic taskId query, you get time_estimate and time_spent. But if you use a parent taskId query, only one of those fields is returned for Subtasks.
Long story short, it just doesn't make any sense how ClickUp has decided what to return when using a parent taskId in conjunction with 'include_subtasks=true'.
It causes our developers to have to loop back into the API to get all relevant subtask metadata.
Richard Mukalian
Also ran into this issue and had to create nested loops to pull all of that data (and as a side-effect, greatly increases the number of API calls to get that data we need)
Luci N.
not on the roadmap
We are closing this feature request as we work to make better use of our feedback boards! Removing old and stale posts will increase the communication between the ClickUp team and our users, as well as allow us to hear more of your great ideas!
If you feel like this request is worth us revisiting, feel free to create a new post for this request!