Which ClickUp timestamp accurately reflects when a task was finished?

Always use `date_closed`. The `date_updated` timestamp changes on minor edits or comments and will cause false positive inclusions.

How do ClickUp Spaces, Folders, and Lists map to product hierarchy?

Map Spaces to top-level Products (e.g. 'Core SaaS'), Folders to Modules (e.g. 'Billing'), and Lists to work categories (e.g. 'Features', 'Bugs').

How do you handle ClickUp custom status names?

ClickUp groups all custom statuses into predefined categories: `open`, `custom`, and `closed`. Filtering for status category `closed` catches every completed task regardless of its label.

Does ClickUp support webhook notification on task completion?

Yes. ClickUp fires the `taskStatusUpdated` webhook event when a task transitions to a closed status.

Map ClickUp Spaces and Closed Tasks to a Weekly Changelog

How to extract completed ClickUp tasks, filter by date_closed, and map Spaces and Lists to clean weekly changelog categories.

Soobrief Team — Product & Engineering, Sooapps · 2026-08-30

In short

Generating a weekly changelog from ClickUp requires querying tasks with `status.type = closed` using the `date_closed` timestamp, mapping ClickUp Spaces to product areas, and categorizing via Lists or Custom Fields. This creates a repeatable release report directly from your project hierarchy.

Generating a weekly changelog from ClickUp requires querying tasks with status.type = closed using the date_closed timestamp, mapping ClickUp Spaces to product areas, and categorizing via Lists or Custom Fields. This creates a repeatable release report directly from your project hierarchy.

ClickUp offers unmatched flexibility in folder structures and custom statuses. However, without strict extraction rules, that flexibility can make compiling a reliable weekly update chaotic.

1. Filtering by `date_closed`

ClickUp stores timestamps in Unix epoch milliseconds. When querying via API:


GET /api/v2/team/:team_id/task?statuses[]=complete&statuses[]=closed&date_closed_gt=1725148800000

Never rely on date_updated, because leaving a comment or adding an attachment on a completed card will bump date_updated and duplicate the task in future reports.

2. Mapping the ClickUp Hierarchy

ClickUp's three-tier hierarchy maps cleanly into release documents:

ClickUp Level	Typical Setup	Changelog Mapping
Space	`Frontend App`, `Backend Infrastructure`	Top-level Section Headline
Folder	`Authentication`, `Analytics`	Sub-feature Grouping
List	`Sprint 24`, `Bug Fixes`	Delivery Timeline & Category

Once configured, completed cards flow automatically into their designated sections without manual sorting.