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

Copy custom field values to another custom field

Madhuri Latha Bhumireddy

I want to copy of custom field values to another custom fields ,as there are duplicate custom fields i need to clean up

custom field name is External issue ID nearly 22 are there only few of them is having more issues rest of them are few.

while using built in scripts in jira cloud i used copy of custom field value to another field

the following is the screen shot i attached

Screenshot 2023-09-06 210108.png

Accepted answers

All comments

JM Perrot

Hello @Madhuri Latha Bhumireddy

I can propose another way, did try to do it by Automation rule ?

Screenshot 2023-09-06 at 17.48.25.png

Regards,

Madhuri Latha BhumiReddy_9m0o3a

I tried but its not working, hope you understand my problem

am having 22 external issue id custom fields with same name having different issues in each field i want to clean up and keep the issues in single field.

Thanks,

Madhuri

JM Perrot

It's not working or it's not the expected result ? What kind of field do you use ? Are they the same type ?

These fields are all display on each issue or do you have only one field among these 22 display by issue ?

Regards,

Marc -Devoteam-

Hi @Madhuri Latha Bhumireddy

The External Issue ID with number is a created field when an project import

Every time this s done a field like this is created with a context to the specific imported project.

"The current behaviour is that we save the value mapped to Issue ID as a custom field. This behaviour is intentional, as it allows users to update the issues based on the earlier used ID in the CSV file."

Also see https://jira.atlassian.com/browse/JRACLOUD-81999

So these fields contain ID values, not actual data.

So you can retain one field and change it's context, to global.

But you can't combine them as when create the 1st value stored in the field is 1, so combining them can't happen, as all already existing fields have the value 1 and a field can't have duplicate information.

Marc -Devoteam-

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud