duplicate custom field jira

[Nour BenAmor]

We have something strange with my JIRa

Duplicate custom fields with identical names are created

Is there something I am doing wrong? Why i have this behavior ?

Note:

I use Jira v7.12.1

[Jack Brickey]

Jira does not prevent you from doing this. You admin(s) must be diligent and not create this issue as it will become challenging to mange to be sure. You need to either get rid of one of them or rename one of them. If you choose to combine the two then I would recommend you first rename one as that will make it easier to combine.

[Nour BenAmor]

I'm a jira's admin . the custom-field are created automatically and i have no idea what causes this behavior.

Am i missing something?

how can i prevent it from happening again?

In my case , it's critical . It may cause problems with customer

help please

[Nour BenAmor]

@Jack Brickey 

By the way , i think this behavior appear when importing a jira-dump into new jira instance.

  Also when i import a new workflow

how can i block the import of custom fields already exist?

[Jack Brickey]

I don’t understand. Importing a Jira-dump? Do you mean you are restoring from a backup? If the instance is new and now custom fields have yet been created and you aren’t doing a merge then duplicates won’t occur. 

[Nour BenAmor]

@Jack Brickey 

yes i mean restoring from a backup

it's true it's a new instance but when i import a workflow, some custom fields are duplicated

[Jack Brickey]

no idea why this would occur. What field/fields are being duplicated? Here are my current theories:

• The duplicate fields are actually in the backup and being restored
• You have a custom field in the backup with a name equal to a Jira system default field (bad form)
• There is a bug
• Some other cause but not apparent under the current info presented here

I would suggest the following course of action.

1. verify that the duplicate custom fields are not in the original backup. if they are stop here. if not...
2. verify that the fields being duplicated are not named the same as Jira system fields. If they are stop here. if not...
3. contact Atlassian Support

[Nour BenAmor]

it seems that it is an already a bug declared:

https://jira.atlassian.com/browse/JRASERVER-37358?_ga=2.178553059.658913727.1574766047-2097356762.1501581392