Include Task ID in a task name
Kimberly Clarkson
From a support ticket:
Automatically include a task's ID in its name either as a prefix or suffix
Log In
Michael
To be clear - this is already possible. The issue is that we can't include the Task ID of the task
being created
. Currently, when adding the Task ID (via automation) as a prefix or suffix, it adds the Task ID of the Task that triggers
the automation https://www.reddit.com/r/clickup/comments/14nl87k/comment/jqvv823/?context=3. That might be helpful to someone somewhere, but not to me. If this isn't what this request is about I'll be more than happy to put in a new request Luci N.
Sean Kilcullen
Merged in a post:
Custom ID (final not temp) in Task name
Steve Kostrey
I use Custom IDs. Is there a way to have the custom ID automatically added to the task name?
This is common in Jira and is an add-on feature in Asana. It's definitely needed in ClickUp!
So for example when I create a task I name it.
"Create images for Blog".
Then when I save it (or when it updates), it applies the Custom ID to the front of the name, like this:
"ABC-45 | Create images for Blog".
This way, when you are working with client ABC you know that it's the correct issue for that client (when you are billing, etc.), and you can easily say in a meeting "let's talk about issue 45...", also when you are searching for an issue in the board view it makes it super easy to find as the search in the regular view doesn't search for custom ID, only the search in the main (or global view) does.
There is a video that explains automation but this solution actually doesn't work for this feature request: https://www.youtube.com/watch?v=7z6bjxmVAvE
You get strange things when it runs. Original name: "This is a task". When the automation runs:
"860pz46wp | TFMG-2678 | 860pz46v3 | this is a test"
"TFMG-" being my custom ID prefix.
It adds the temp id and then the (final) Custom ID and then the Temp ID again. It's a mess. :-(
Jeff Manning
Agreed, nothing is worse then referencing a ticket ID and then having no easy way to find it in the system.
O
Olivier Berthelot
THAT would be amazing. I was looking exactly for something like this. But it need to also be merged with custom taskIDs for list and folders.
We are actually doing it manually at every task creation. The reason is we often have similar task names like 'Finish the report' or 'Review a document', etc. Adding the custom task ID make it clear for what project the task is related to, without having to browse around.
A
Alexandra Wiedermann-Huczek
Add Task Name prefix / suffix to Automation options. This should allow any field to be added to a Task's name when it is created;
i.e. Task ID-Task Name or Task Name-Custom Field:Confidential.