Feature Requests

The 3.0 update seems like a natural time to add this functionality.

Related to https://api.clickup.com/api/v2/task/abcdef/comment API endpoint. Allow using markdown syntax (tables, h1, embedded images etc) while adding a comment to a task. It is possible to use markdown with markdown_content paragraph while creating a new task. I would expect the same behaviour for comments.

I just tried to create a new sprint folder and set the first sprint on the same index as our other sprints (Sprint 15 for 31/07/23 to 12/08/23) but ClickUp won't let me choose to start on Sprint 15, I'm forced to start on Sprint 1. I had to duplicate another sprint folder without the tasks to get what I want. I don't understand why it was possible before and not anymore. It is useful, we need this feature.

Custom task id takes a long time (according to technical support team - up to 5 mins) to be generated in the back end and to become retrievable via api. This is not acceptable as a work productivity tool - imagine creating a task and having to sit in front of your screen for 5 mins to wait for your custom task id to be generated (and subsequently downstream webhook automations such as folder creation with custom task id prefix to be created). Much like many other posts here, native task IDs are not suitable because they are a jumble of random characters which is not helpful to end-users to organize their tasks chronologically.

FCG

We are using the ClickUp API to update a variety of custom field types, which has significantly streamlined our workflow. However, we've noticed that it is currently not possible to update custom fields of type "file" via the API. This limitation requires us to manually complete this step, which disrupts our otherwise fully automated task updating process. Adding support for updating file-type custom fields through the API would greatly enhance our efficiency and improve the overall user experience. Thank you for considering this enhancement! Please let us know if you need any additional details or examples of how this feature could benefit users like us.

We currently use the API to integrate ClickUp with custom enterprise software systems and databases. Currently, the API actions have to be performed under a user account so all of these automated actions appear to be from a single user. It would be useful for the workspace owner to be able to generate an API Key where the actions are shown to be performed by an API Bot, similar to how automations show that they are performed by ClickBot.

Description: Currently, while task descriptions support Markdown formatting through the API, long text Custom Fields do not. Implementing Markdown support for these fields would allow for consistent rich text formatting across tasks and Custom Fields, enhancing data presentation and user experience. ​I am working on replicating Azure DevOps' commit history view within ClickUp tasks for my team. To achieve this, I'm using a combination of Webhooks and the ClickUp REST API. Implementing Markdown support for long text Custom Fields via the API would greatly assist in this endeavor. Thanks!

The integration of ClickUp’s timesheets with external billing platforms, such as OpenEhr, has faced significant challenges due to the lack of API support for timesheet approvals. This limitation has resulted in complex and inefficient workflows, requiring additional development work and support resources to manage frequent issues. Lack of API Support for Timesheet Approvals: Issue: The absence of API endpoints for timesheet approvals prevents seamless integration with billing platforms like OpenEhr. Impact: Changes made in ClickUp are not consistently reflected through the API, leading to discrepancies and delays. Complexity of Integration: Issue: The integration process becomes highly complex without proper API support, requiring extensive development work and a dedicated help desk to address recurring problems. Impact: This complexity has caused significant delays, with users unable to fully utilize ClickUp’s intended functionality for over a year. Proposed Solution: Develop a public API for Timesheet Approvals with the following capabilities: Support for submitting, approving, and managing timesheets via API. Real-time synchronization of changes made in ClickUp with external systems. Webhook notifications for approval events to enhance visibility and reduce delays. This feature is critical to enable seamless integration with billing platforms, reduce operational complexity, and ensure that users can fully leverage ClickUp’s timesheet functionality without incurring unnecessary costs or delays.

There are 2 requests: Allow a Users search/filter api that allows look up by email or user name. Also, highly recommend making the user details api accessible to customers at all levels rather than enterprise only. I'm trying to sync clickup groups with oncall rotations from various sources, and I'd like to be able to look up user by email to get the user's clickup ID and then use it to update the group.