Custom Field for Unique Number

[Guntis Zoldners]

Hello, Can I make a unique number field to import issues to Jira so they do not duplicate with the next import?

[Bill Sheboy]

Hi @Guntis Zoldners -- Welcome to the Atlassian Community!

What problem are you trying to solve by doing this?  That is, "why do this?"  Knowing that may help the community to offer better suggestions.

Until we know that...the Issue Key and Issue Id are already unique identifiers within the site's issues.

Kind regards,
Bill

[Guntis Zoldners]

Thank you for the warm welcome!

To clarify, I’m looking for a way to ensure unique identifiers during regular imports, as there’s a chance of accidental duplication with each batch. Specifically, I need a custom field that can consistently enforce uniqueness across imports in a Jira Cloud instance. The goal is to prevent re-imported issues from creating duplicates, ideally by recognizing if an identifier already exists in the system.

I understand Jira natively provides Issue Key and ID for internal uniqueness. However, these don’t apply across external imports. If anyone has insights on plugins or methods that work in Jira Cloud to flag or prevent duplicates based on custom field criteria, I’d greatly appreciate it!

[Alex Koxaras _Relational_]

Hi @Guntis Zoldners and welcome to the community,

Out of the box Jira doesn't provide this functionality. However you could use this free app https://marketplace.atlassian.com/apps/1211043/unique-regex-custom-field?hosting=datacenter&tab=overview, which to be honest I haven't tested it. It might suit your needs.

[Marc - Devoteam]

Hi @Alex Koxaras _Relational_ 

You could be right, only that this app is not for Cloud instances only on-prem.

Stated to the tags the user is on Cloud

[Alex Koxaras _Relational_]

Ohh my bad! Indeed it is for DC version.

Then the other way to approach this issue @Guntis Zoldners would be to try and create a new forge app, for a custom field, which will include regex setup screen, similar to the one of the DC version. I have in the past created custom fields using forge, but not regex ones.

[Marc - Devoteam]

HI @Guntis Zoldners 

Welcome to the community.

The only option you have is to have a custom number field and to not use this anymore in a future import.

There is no unique option in Jira fields.