Custom Task ID at the Workspace, Folder, List level, subtask

Rich Manzana
Current this is only available at the space level. I'd like create Custom Task IDs at all levels. Workspace, space, folder, list.
Log In
Activity Feed
Sort by

Kristy Adams
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!

Rodrigo Carballo
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.

Joanna Cendrowski
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>.

Joachim Chauveheid
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

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

Saskia Mardi
Yes please - currently I need so many spaces to be able to have different custom task ids. Also the ability to rest numbering of the custom task ID would be great.

Joanna Cendrowski
We would love this at the folder level at least. It'd be a game changer! We have Spaces FOR ALL our clients because we need the custom task IDs to be client-specific (for Github and Harvest time tracking). But would love a space for out Support clients, where each folder is a different support client. It would allow us an easy view of ALL active tickets in Support.

Nhel Rosal
Upvote - We currently need this in our project this help allot for setting up transaction No. and Membership ID in the same space

Collin Bentley
Upvote — very desirable functionality at least at the list level, as well as ability to define Custom Task IDs for different types of tasks (custom defined tasks) within a space. For example, Incident task type should have the INC-123 custom ID, while Change task types should have CHG-123 custom ID.
A
Adrian Berca
Upvote
Load More
→