Hey @Richard_Sather is there a way to only apply the custom ID to the custom task type it was created for instead of all tasks created? If not is there another votey thing for that? 
Hi @Ian_Layton-Smith , IDs are populated to tasks that are added to a project that contains the ID field. So you could just have the ID field in a certain project that you only add (via a rule) your certain tasks (or certain task types, in your case) that you want to get an ID applied to them, while keeping all the other tasks in the (main) project.
I just posted the same thing and then found your post here.
Give us the OPTION!!
The ID field is really useful and has helpfed me improve some of the workflows I have.
Currently, when I set it up on an intake project, any task and subtask created will get an new ID.
While I understand the logic, I like th ehave the flexibility to decide if I want subtasks included (inherit the field or not).
Reason:
A new intake request comes in - New ID is created - ID1
The work gets discussed and evaluated and few subtasks are added for further evaluation.
Currently:
subtask 1 is ID 2
subtask 2 is ID3
Desired outcome 1:
subtask 1 - no ID
subtask 2 - no ID
OR Desired outcome 2:
Subtask 1 - ID1-1
Subtask 2 - ID1-2
This makes reporting a lot more meaningful.
2 Likes
Hi team,
Iād like to submit a feature request: could we have the option to toggle, or hide the ID numbers on subtasks? They can be visually distracting, and having a toggle to show or hide them would make boards and lists much cleaner.
Iāve also found this thread requesting the same that goes back to 2023:
Thanks for considering!
Hi @JoAnne_Conran , if your feedback post is the same as mine that you have reference, itās best to have one for everyone can vote on. If you agree, do you mind if I merge your post into mine?
My apologies Richard, I did vote on your post but was advised it was a Forum post only, and was provided with a link to submit FE requests specifically. I will inform the user who provided the link they feed into the space space.
Hi again @Richard_Sather Unfortunately it doesnāt look like I have permission to delete the post so Iāve flagged to comment and requested it be deleted.
No worries, @JoAnne_Conran Iāve merged everything into this one
1 Like
Was surprised to find that we canāt restrict the ID field to only parent tasks today, since itās standard on just about every other customization field. Iād offered to turn it off for a colleague, now Iāll have to tell them I canāt do that. Itās not a huge deal for my projects, weāll probably ignore the unique subtask ID, itās just weird that this wasnāt considered and inflates the ID numbers we really have in case we need to report on it.
2 Likes
Hi All,
Iāve been using the āIDā custom field which can automatically rename tasks in sequence i.e unique idenfier āTRBā will then rename TRB-1, TRB-2, TRB-3, etcā¦
The issue I have is that I want to use this operation on parent tasks only. It currently also generates a specific number in sequence for all related subtasks.
The use case is a Quality control log, so we need a unique reference for each ātaskā, but not for the subtasks, which are the actions for the technicians. But the ālogged jobā is just the task so the unique reference needs to be for the parent tasks only.
Wishing to the Asana Unicorns that there is a solution 
1 Like
Hi @Rebecca_Hassett,
I merged your post with an existing topic for this request. Be sure to add your vote for it at the top of the thread.
Added my vote!