-
Suggestion
-
Resolution: Unresolved
-
None
-
53
-
16
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Steps to repro:
1. Create some custom fields and use them in a workflow
2. Export the workflow from JIRA
3. Import the same workflow back in
Expected:
No new fields should be created since the same type of custom field, with the same name already exists
Actual:
A new set of custom fields is created.
- relates to
-
- Closed
- mentioned in
-
![[Atlassian Documentation] Page](/images/icons/generic_link_16.png "[Atlassian Documentation] Page")
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRASERVER-37358] Workflow import creates duplicate custom fields
Will this be ever solved? Being able to opt out of re-creating custom fields should be readily available when importing a workflow.
There's no workaround in the description, but it's possible to edit the export file and replace the relevant field IDs. You don't even need to access the database or use APIs, they can be checked in the Custom fields section of the (sys)admin panel by hovering over blue links or actions.
10 years since this was raised. This seriously hampers developing changes in another environment. Duplicate fields are the last thing you want. Why is it so hard to migrate project between Jira instances. The UI tooling is minimal, REST APIs are incomplete and then when there is a feature like this it turns out to be dangerous to use.
I cannot overstate the amount of HOURS spent correcting custom fields after import, please save me
+1 it hurts a lot, really. Created quite complicated wf on testing environment and after long testing and mending and all cannot import it to prod due to this error and will have to to recreate it from scratch manually... fields that Jira is trying to recreate exist with the same type, name and ID! doublechecked it. So really really bad.
I've observed when importing a workflow from another instance, if name, id and context are not an exact match, Jira creates a new field. This makes sence because Jira cannot make assumptions based just on field name. The example above is using newly created fields, exporting and importing into the same instance, so I think in that case a re-index after creating the fields may fix that. I haven't tested that.
However, and this is what the real problem is, when Jira creates new fields on workflow import, existing filters using the existing custom fields, switch over to the new fields and it breaks the filters. This behavour is the super buggy part.
It would be nice to have a field mapping screen on workflow import based on field names and the user could set mapping, even if id or context wasn't a match.
Same problem here. It's difficult to clean up. Please fix this.
This is insane we need this fixed. For Statuses it lets you choose what to map to... Why not do the same for custom fields