Connector Improvement: Support "ViewTask" entity in ClickUp Connector
Completed
Our business uses the ClickUp Sprint View to manage our engineering sprint process.
The Sprint View utilizes the "ListViews" feature under the hood. Tasks that are added to a sprint are represented & identified as "ViewTasks" within the API, attached to a "ListViewId": https://clickup.com/api/clickupreference/operation/GetViewTasks/
https://clickup.com/api/clickupreference/operation/GetListViews/
To properly calculate sprint velocity, burndown, and other sprint metrics, we will need both the ListViews, as well as the ViewTasks entities to be synced.
It would also be critical to "Include Closed" tasks, and "Include Subtasks" within the ViewTasks fetch.
-
Official comment
Hi Chris,
Thanks for raising this request and for clearly explaining how you use ClickUp’s Sprint View. We understand the importance of syncing the necessary sprint data to support metrics like velocity and burndown.
We’ve now released this feature, and your feedback played a meaningful role in helping us get here. Thank you for contributing; it helps shape our roadmap.
Thank you,
Sisan
Please sign in to leave a comment.
Comments
1 comment