have JIRA auto-assign a unique number to each new issue?

Question

It's been a while ago when I used JIRA on a stand-alone server.

Somehow, I forgot how, we managed to have a unique number assigned by the system to each new issue.

This next could be used as a hyperlink in other applications.

Can someone please point me where to find info on how to add this?

Thanks, Edgar

Jack Brickey · Accepted Answer

Hi Edgar and welcome to the Community. When you say a unique number do you mean something different than the issuekey itself? Every issue in Jira will be created w/ an issuekey that consists of the project key and a number starting at "1" and progressing from there. This issuekey is a link in Jira to the actual issue. I'm unsure why you would need something duplicating this but I may be misunderstanding your needs.

Tomas Gustavsson_mf0n45 · Accepted Answer

Maybe i totally misunderstand you, but this is not something you have to add, or configure.
it is normal functionality in Jira, each ticket get it's unique number, build up on

Project key, and a number.

e.g project A

will have tickets called A-1, A-1, A-3 and so fourth. each ticket will have is't on link.
built up on jira instance name and ticket id

https://jira/browse/A-3

Nic Brough -Adaptavist- · Accepted Answer

Jira already has two unique ids for an issue, which gives you three options * Use the issue key - gives you a url automatically, https://yourjira/browse/xxx-###. This is not numeric, it's - and can change if an issue moves projects (Although Jira tracks that it has moved, so people landing on an old url will be redirected to the new one. * There is a numeric id in the database. Unique, never changes, but not generally exposed to the users and cannot be converted to a URL. A scripted field can expose it really easily (the script is almost as short as "return issue.getId()" ) * Make your own field that does it - this is quite hard work itself, just to get another unique number (you have to account for people creating issues at the same time, which is not trivial), and you have to do a load more work to get it usable as a url Note that with the second and third approaches, people will generally ignore them in favour of the issue key, as the issue key is used everywhere, is unique, has a url and so-on. It is intended to be the unique identifier for humans talking about Jira issues.