Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Create a new project key with automate Edited


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?


3 answers

1 vote

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.

0 votes
John Funk Community Leader Dec 07, 2020

Hi Manu - Welcome to the Atlassian Community!

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

Thank you for your answers.

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

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

Please do not accept answers that are not answers.

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.

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

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...

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

120 views 7 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you