nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to migrate data from issue custom field to another custom field

Saqib Dar

Hi team,

How to migrate data from one issue custom field to another custom field on a same issue.

We are planning to change custom field type from single user picker to multi user picker.

So in this case i have to create a new custom field and migrate date from old to new custom field

Accepted answers

Florian Bonniec

Hi @Saqib Dar

There is couple of way to do it, it will depend on the volume of issue you have.

You can export the issue then import them back by mapping the old field values with the new one.

You can also use apps such Scriptrunner which have a built-in script that copy field values from one field to another.

If there is not much option in the field you can do a JQL for each option then update them an set the new field values.

Regards

All comments

Florian Bonniec

Hi @Saqib Dar

There is couple of way to do it, it will depend on the volume of issue you have.

You can export the issue then import them back by mapping the old field values with the new one.

You can also use apps such Scriptrunner which have a built-in script that copy field values from one field to another.

If there is not much option in the field you can do a JQL for each option then update them an set the new field values.

Regards

Joseph Chung Yin

@Saqib Dar -

The simplest way just using out of the box functionality are the following -

1) Export your existing issues where the original field is populated into a csv file. The csv file for the custom field should contain the single user field value.

2) Add your new multi-user picker field for the affected project(s).

3) Use your csv file generated in step 1 as a base to conduct external system import back into your env. This time the original single user field column will serve as the import field for your new custom fields. Take a look at this link in regards to External System Import process to update your existing issues. NOTE - You need to map the issue key during the import process to populate the new field. https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html

4) Validate the outcome. Once the validation is completed, then you can just remove the original field from your affected project(s).

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.

Saqib Dar

@Florian Bonniec Thanks for your response the most easiet way is to do through scriptrunner

Nirmani Kalakheti

@Saqib Dar , @Florian Bonniec I tried SR for Jira but the target doesn't have options. I have a version picker CF and I need to move the versions from this CF to Affects Version/s(System Field).

Any idea or any other options?

Florian Bonniec

Hi @Nirmani Kalakheti

Version should exist in teh target project. As long as they have the same name it should be able to map them.

If it's not the case Import/Export should work or a SR script that for each version get the equivalent version on the target version.

Regards

Michael Aglas_ocluj7

welcome to the 21st century

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-service-management

jira-service-management-server