Upvote - We currently need this in my company.

We have a structure of

Space = Client

Folder/List = contract / project

It would be so helpful to have the task ids reflect each project and not just the client they refer to.

Having Custom Task IDs available at the Workspace, Folder, List, or even Subtask level would provide much more flexibility and make organisation far easier, especially for users who want unique identifiers for different projects or processes without the overhead of creating a new Space for each organisation easier, especially for users who want unique identifiers for different projects or processes without the overhead of creating a new Space for each one.

#Current Limitations

>Custom Task IDs are only available at the Space level. All folders and lists within a Space share the same prefix and sequence.

>Needing separate Spaces for each prefix can quickly become cumbersome, especially if you want to keep related work together or use cross-list automations.

>Segregating work across Spaces introduces several limitations:

>>You can’t easily move tasks between Spaces without changing their Custom Task ID and losing some context.

>>Automations, reporting, and dashboards are more complex to centralise.

>>Permissions, views, and integrations may need to be duplicated or managed separately.

#Why This Suggestion Makes Sense

>Workspace-level IDs would enable global, unique identifiers.

>Folder/List-level IDs would let you organise and refer to tasks in a way that matches your actual workflow, without artificial boundaries.

>Subtask-level IDs would facilitate granular tracking in complex projects.

This is needed in some level of urgency! Please any updates as having more than one dev project in a space (as it should be) is a pain, having to duplicate spaces for each project and having multiple spaces for one client is really not great!

We have multiple tasks with the same description/heading for different projects - there is no practical way around this. Each project has it's own code that is applicable to our financial software and current paper based model. With in this code it identifies who the sales person is, job location by town/suburb and the type of job (new, refurbishment etc etc). These codes are invaluable to our business. We would like to be able to have the same code attached to each task for that project list (usually 1 project = 1 list). There is so much information attached to that code, its automatically there for every task. Then the ClickUp item number gets put on the end - it would be perfect! We would also benefit at the folder level. Please plan to put this one in place.

We're using custom task IDs to automatically generate a unique project code for each project we open, e.g. PRJ-1234.

Ideally, we would have stored our Master Project List in our Admin space. But because we couldn't apply the custom ID to a single list, we had to go out and create a separate space just to hold the Master Project list. That was the only way to ensure that the custom ID was used for a task in the Master Project list and nowhere else.

It would be great to be able to set Custom IDs at a lower level than Space.

OMG... I would love this, this would make integrations more functional.

I was looking if this was possible and found this thread. I have been using Memtime recently and you can't always tell which client the task is. All our clients are in one space with their own folder and list.

There is no use to have custom task ID at the space level, it would only be useful to have it at the folder or list level.

I have been using Harvest integrated with Clickup for years, so when time is tracked you need to select the client anyway but if the client prefix was in the task ID, it would be super easy to see if any errors were made.

Gosh, I hope this is something that can be implemented soon, it would be awesome!

In our company, we use a shared SPACE to host several teams (FOLDERs). Some teams prefer to use custom IDs, while others do not. Implementing a feature that accommodates both preferences would help us meet everyone's needs. Currently, our only alternative is to separate the teams into different spaces, which is not ideal for our employees' end-user experience.

Yes, this would be a game-changer for our space. We have spaces by client, but different projects/SOWs within one client space. Would make it so much easier to check that time-sheets are allocating time to the right SOW/bucket of money if the task ID was set per folder. I could name it ACME-SOW12-<ticketnumber>.

We'd really need something like this. Using the space-level id is not super practical.

Maybe I could set up an automation that overwrite the custom id at task creation. But it would be more handy to have that built-in, especially for git project integration

any update on this? When will this be implemented? People are waiting on this feature for quiet a long time now.