Can we have series number in Jira cloud custom fields incremented whenever a new work item got creat

[sravani vennapusa]

Can we have series number in Jira cloud custom fields incremented whenever a new work item got created as follows (for bug -1 the field should beTR0000001, for bug-2 the field should be TR0000002) like that? can anyone please suggest?

Thanks.

[Sebastian Krzewiński]

Hi @sravani vennapusa 

First of all why? You have unique issue key.

Secondly you can use automation and number from issue key add to TR000... in text field. You need to create logic to add correct number of '0' depending on number from issue key.

Due that TR00000... is a combination of letters and numbers you can't use math smart values.

Regards,

Seba

[Shivam Sharma - Optimizory]

Hi @sravani vennapusa ,

Totally doable in Jira; the question is just how clean you want the sequence to be. Native automation can get you the TR0000001 format using a smart value like TR{{issue.key.substringAfter("-").leftPad(7,"0")}}, but the number stays tied to the Jira work item key. So you'll see gaps when work items get deleted; the same counter runs across all work item types, and existing work items won't get a value unless you backfill them.

If you want a proper independent sequence, Jira add-on "Custom ID for Jira" handles exactly this. You define a pattern like TR0000001 once on the Custom ID home page, and every new work item gets the next ID automatically. You can also set different patterns per work item type or project, so Bugs, Stories, and Tasks can each follow their own numbering scheme.

To get started:

• 📖 Introduction
• 📖 Create a Custom ID

You can find the app on the Atlassian Marketplace. And also, there's not any cost for this; it's a free app.

Happy to help if you have more questions!

[Arkadiusz Wroblewski]

Hello @sravani vennapusa 

Something like that: TR{{issue.key.substringAfter("-").leftPad(7,"0")}}

That should give you: 

ABC-1 → TR0000001
ABC-25 → TR0000025

Just keep in mind that this is still tied directly to the main Jira issue key number, so it won't give you a separate, independent counter per issue type. If you need a strict, completely separate sequence just for Bugs, I wouldn't recommend trying to build that with native Jira automation alone and take a look for Forge Integration or App.