In this particular case using a naming convention is probably the best answer.
If you already have a naming convention for projects, you could just reuse that to prevent confusion :)

Thanks AgitatedDove14 and TimelyMouse69 . The intention was to have some traceability between the two setups. I think the best way is to enforce some naming convention (for project and name) so we can know how they are related? Any better suggestions?

OddShrimp85
the Task id is UUID that is generated by the backend server, there is no real way to force it to have a specific value 😞

You can use the same project name and the same Taskname if that helps?

I don't think it's possible to set a custom ID if it doesn't exist yet. But I'll double check!