Also, being able to search by the Task ID is a super handy feature that we used to have, but which seems to have disappeared with the upgrade to 4.0.

Adding to this feature request...

All of the previously-mentioned places, as well as and linked task references.

The Custom Task ID is what we use in our vernacular when discussing or mentioning a task. Having the option to always display this would be super beneficial.

Having at all levels would be good. Better would be to be able to append via the hierarchy. Example Workspace-Folder-TaskType-Task--> HR-BEN-MED-0025

This is super useful for us. As our folders in the space represent different things. If the task ID is distinguishable, that would be great

We just hit this issue. IMO, the default task ID format is not human-friendly, the standard should be PREFIX-{task_number}.

Has this had any movement yet? This is a major issue for our company and may be a deal breaker!

any updates on this?

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!