Create a new project key with automate

[e.bouchex]

Hi,

I would like keys follow each other for the task, but not for the sub-task. It seem not possible.
I would like to create a new field and to use automate to generate a new key.

Automate has to read the field of the last created task ("M20001" for example), add +1 to transform to "M20002" and then to edite the field of the new task to write "M20002".

Do you aldready done someting like that?

Thanks.
Manu

[Nic Brough -Adaptavist-]

You won't be able to do that in Cloud, and it's actually a lot harder than you think in server as well - you will end up with gaps and duplicates.

Frankly, don't bother.  Your sequenced key is of no real use to the end-users.

[e.bouchex]

Thank you for your answers.

So I have to find another way to work with the key...

[Nic Brough -Adaptavist-]

Probably not.

You have not told us why you think you want to do this.  If you could explain the problem you are trying to solve by generating a redundant key, we might be able to help you find a better solution

[Nic Brough -Adaptavist-]

Please do not accept answers that are not answers.

[e.bouchex]

I created a project named "modification" in order to open tickets for each modification request. All of these tickets have a specific number (the key) and each of them follow the previous.
In these tickets, I would like to use subtasks and define user. But these subtasks use the same key than the tasks... so the tasks keys don't following.

[Nic Brough -Adaptavist-]

Ok, but why do you think you want the keys to "follow"?

[e.bouchex]

If we use key for the subtasks, our current key format will become to small and we will change it.
In the same time, it is less user friendly...

[Nic Brough -Adaptavist-]

Neither of those are any reason to do what you've proposed.  I don't see any benefit from having a non-useful non-unique key.

[John Funk]

Hi Manu - Welcome to the Atlassian Community!

I am not aware of any way this is possible in Jira Cloud.