You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have recently started our ISO certifications. Something that we are looking to implement across the board in our company is something like a "Job Number" per project we do to track everything about this project across all our platforms. All the way from the Quote phase through to procuring goods to invoicing to project tickets etc...
So I got thinking about how can I make this happen in Jira Cloud.
I was thinking could I create a new custom field and have it auto-populate with a random number. But only have this custom field on a particular task type this way I would not have random number on all tickets just on the tickets I need them to be.
It is not clear what this job number is for - you talk about "per project", but then start saying you want one on individual issues?
I do not understand what benefit a random and unique id would add. I understand you want to refer to it in other systems and places, but I don't see the advantage of not just using the existing Jira keys if that's where you would be generating the job number (if job numbers are project things, use the project id. If it's by issue, then use the issue key!)