Feature Requests

Currently the Sprint Reporting Widgets (such as the Sprint Task Report & Sprint Burndown Chart) have data source options for "Current Sprint", "Previous Sprint" and "Specific Sprint". Having this flexibility is great, however, there's a few issues with these options. If you select "Current Sprint" but you have not yet started the sprint, it will not display any data (making it difficult to plan the sprint without the Sprint Task Report). Additionally, this renders the Sprint Reporting dashboard useless when viewing historic sprints If you select "Specific Sprint", you have to manually edit this each time a new sprint is created. If there was a way in the sprint template to have it automatically select the sprint being created here, rather than whatever sprint was used to update the sprint template, that would be better. Ideally, there should be another data source option to use the "parent sprint", so if I'm looking at "Sprint 1", it'll use the "Sprint 1" data and If I'm looking at "Sprint 2", it'll use the "Sprint 2" data without having to edit each widget to select a specific sprint.

I would like to request an option in ClickUp to prevent subtasks from automatically consuming Custom Task IDs when the Custom Task IDs ClickApp is enabled. In many workflows, subtasks are used for granular breakdowns and do not require unique, sequential custom IDs—reserving these for top-level tasks would help maintain a cleaner, more meaningful ID sequence and avoid unnecessary gaps or “wasted” IDs. Proposed Solution: Add a setting to the Custom Task IDs ClickApp or Space settings that allows admins to choose whether subtasks should receive custom IDs. If disabled, only parent tasks would be assigned a custom task ID, while subtasks would retain their internal ClickUp ID but not consume a custom ID from the sequence. Benefits: Preserves the custom ID sequence for high-level tasks. Reduces confusion and clutter in workspaces with heavy subtask usage. Provides more flexibility for teams with different task structuring preferences.

Currently all sprints are in US formatting of MM/DD, I can't seem to change this in settings either. So hard to read when you're used to DD/MM - Please help

For computer programming/website development we can have 0 (zero) value tickets. Problem: Currently, if the sprint points column is left blank it is considered to have 0 points associated with it. The problem with this is that we don't know if we just forgot to assign a value to this ticket or it infact has zero value to it. It would be easier Solution: Please allow us to save the number 0 for point values.

When viewing a task in list view, the “Add to Sprint” button is visible and accessible. However, when I open the task detail view, this button is missing. It appears that the option to add a task to a sprint is only available through the list view. This creates a lot of unnecessary manual work. For example: When developers send me multiple task links (often 10+), I can’t add them to a sprint directly. I have to manually search for each task in list view just to press “Add to Sprint”. This is especially time-consuming when managing multiple projects, each with multiple developers and new sprints every week. Please consider making the “Add to Sprint” button available directly in the task detail view as well. It would significantly improve workflow efficiency and reduce frustration for users managing agile teams.

Hi there, first and foremost, thank you for continually improving the platform! We’d like to request a feature that allows setting team member capacity specific to individual teams and Sprints, rather than applying it globally across the account. At Usheru, we have three development teams, each working from separate Sprint boards. Several developers are assigned to two or more teams simultaneously. Currently, capacity settings are applied account-wide, which doesn't accurately reflect team members’ availability for each specific Sprint. Proposed Enhancement: Enable capacity allocation per team per Sprint, so team members can have different allocations based on the team and the Sprint they're working on. This improvement would significantly enhance Sprint planning and help ensure realistic workload distribution across overlapping teams. Thank you for considering this!

a field should automatically track and display all the sprints a task or subtask has previously been part of—not just the current sprint. This would allow you to see the full sprint history for each task, rather than only showing its current sprint location.

I accidentally started my sprint folder on the second sprint, such that Sprint 2 is marked as Sprint 1, and when I tried to add the first sprint for reference it marked that one as Sprint 2. I want to swap the index of those two sprints. (actually they're more like sprint 1 and sprint 1.5, but I don't need non-integer indices) Since I have to include {INDEX} in the name, I'm now stuck with my two first sprints being labeled "Sprint 1.5: 1" and "Sprint 1: 2" There are similar feature requests already, but they seem to focus on skipping forward or looping back indices, when I specifically want to change the index of a previous existing sprint.

Hello, Team ClickUp! I would like to suggest adding management endpoints, especially for creating Sprints. The currently available automations are interesting, however, making the endpoint available would facilitate the implementation of customized automations for specific demands, as is the case of my company.

In the Scrum dev template, you can track pull requests in Github, Gitlabs, and Bitbucket. I would love to see this ability extended to include Azure DevOps to make this feature useful to those of us who use it to store our code repositories.