We're evaluating ClickUp as a potential Jira replacement. ~200 engineers, heavy CI/CD focus.
Primary concerns:
* Can it handle complex branch/release workflows?
* Integration with GitLab/GitHub for automated status updates?
* Performance with that many concurrent users on boards and dashboards.
Looking for real-world data on:
* How you managed the migration of active sprints.
* Any deal-breaker limitations in the API for automation.
* Whether the hierarchical structure (Spaces > Folders > Lists) scales or becomes a bottleneck.
Ship fast, review slower
Used it for about a year with a team half that size, also heavy CI/CD. Your API concerns are valid, it's a bit of a mess. Their webhook system is flaky for real-time status updates, we ended up polling for important state changes like merge request status. It just wasn't reliable enough to gate deployments.
The hierarchy doesn't scale. You'll spend more time debating where to put a ticket in Spaces > Folders > Lists than actually working on it. For complex branch workflows, you'll be fighting the tool more than it helps you. Jira is a bloated beast, but its API is at least stable.
Migrating active sprints was a manual nightmare, frankly. The automation story is weak. If your CI/CD pipelines are non-trivial, ClickUp becomes a bottleneck, not a facilitator.
null
We ran benchmarks on ClickUp's API during a similar evaluation for a 150-person data team. The latency for updating a task status via webhook, from GitLab merge to ClickUp board refresh, averaged 8-12 seconds. For 10% of requests, it spiked above 30 seconds. That's not acceptable for CI/CD gates.
The hierarchy becomes a data modeling problem. You'll end up with naming conventions like `eng-prod-ci-failures` for a Folder just to make its purpose clear, because the nesting lacks clear ownership tags at each level. It creates friction for automated ticket creation - your scripts need to know the exact Space/Folder/List ID path.
On performance, we observed dashboard load times of 4-7 seconds for boards with over 300 active sprint items when 50+ users were concurrently online. It felt sluggish. Jira is slow for different reasons, but ClickUp's slowness stems from over-flexibility - everything is a custom field lookup.