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; } } }

Is there a way to clone a custom field which is a select list to a new field with different name?

Rompicherla Kalyani

Hi Team,

I would like to know if there is a way to clone a custom field which is a select list to a new field with different name?

Or else shall we export the values from existing and import it again for adding values on new select list custom field.

My custom field has almost 200 values which is very much time taking to copy paste one by one

Please let me know if this is possible.

Thanks.

@Mark Segall

Accepted answers

Eugenio Onofre_v78igo

Hi @Rompicherla Kalyani

Unfortunately there is no default feature from Jira that allow you to clone/copy fields.
One possible workaround would be creating the new field through the API, but you would still need to have the more than 200 values as a text.

Please remember to accept this answer in case it helps you resolve your question as it may also help other community members in the future.

Regards,
Eugenio

All comments

Eugenio Onofre_v78igo

Hi @Rompicherla Kalyani

Please remember to accept this answer in case it helps you resolve your question as it may also help other community members in the future.

Regards,
Eugenio

Jerrold - Empyra

Hi @Rompicherla Kalyani

when you mention it has 200 values do you mean that the custom field has 200 issues with the values or one issue has a custom filed value which is more than 200 values as a text?

If it is the 200 issues case then we can use the following method

We can utilize an automation rule to transfer the values from custom field A to custom field B. However, it is crucial to ensure that both custom fields have identical values, particularly in terms of select list options. The automation rule offers a quicker and simpler solution compared to import and export methods. Allow me to illustrate how the automation rule functions using an example: imagine "change reason" as the select list custom field, where you wish to copy the values from, and "change risk" as the new custom field where you want these values pasted into.

Custom field A - change reason

Custom field B - change risk

Copying values from the change reason to the change risk. To automate this process, we require a JQL query that provides us with a list of issues that have change reason values. We can use the following JQL query: "Change reason[Dropdown]" is not EMPTY. This query will retrieve all the issues that have a value in the change reason custom field.

Automation rule -

Trigger is schedule issue

We have selected "Run a JQL search" and will execute actions for each issue in the query. "Change reason[Dropdown]" field is not empty in the JQL, and make sure to uncheck the option to only include issues that have changed since the last time this rule was executed.

testing 123334.PNG

2.The Action will be edit issues

testing 12333444.PNG

Please select the field that you would like to copy to custom field B - change the risk.

After selecting, please navigate to the three dots and choose the "Copy" option.

Once you click on "Copy," it will display as "Copy Change risk" from the current issue you have just clicked on. Then, a window will pop out containing the issue to copy value from, which will be the current issue, and the field to copy value from, which will be the custom field A.

Once you have provided the custom field name and updated it alongside the return rules, you will notice three dots. If you select them, you will find the option to run the rule.

Once you enable the "Run Rule" option, the automation will execute and copy values from custom field A to B for all issues specified in the provided JQL.