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 do I copy the text contents from one field to another text field in Jira (cloud)?

Gene Sullivant

An issue gets Transitioned from a Jira Service Management project to a Jira project and I need to copy the contents from one custom text field to another custom text field. I tried to use the More Options with an "update" but it didn't work.

I place the original field in the Jira project and added it to the Issue Type so I can get the data copied from the original issue. But that Team doesn't want that field, they want the same field type but with a different name.

I need the values from the JSM field to get copied in to the Jira field (again both are text fields).

Thanks!

Accepted answers

All comments

Manoj Kumar Gangwar

Hi @Gene Sullivant please check below thread.

https://community.atlassian.com/t5/Jira-questions/How-to-copy-text-field-between-projects/qaq-p/1375287

Gene Sullivant

Those don't get to the solution I need.

I think if the custom Text field that needs the data needs a smart value to copy the value from the "original field" to the new field.

Marcela Junyent_scufs0

You can just create an automation to copy the content where the trigger is the transition and use the edit action to edit the destination field.

Also JWME has that feature as postfunctions options.

Gene Sullivant

Yes, except that the target field has a different name than the Trigger issue field.

Gene Sullivant

But the it needs a smart value to put the values from the Request Contact field into the BL Contact field.

What does that look like? I have tried several combinations and it doesn't allow be to just say copy from Request Contact field from trigger issue.

Bill Sheboy

Hi @Gene Sullivant

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!

Until we see those...

To find the supported smart values, and their correct name and custom field id, please use this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

The basic steps are to identify an example issue with your fields, use a browser tab to call the REST API to load the data, and the search on the page for your field (e.g., with CTRL-F).

Kind regards,
Bill

Katrina Lieber

Hi Gene,

One potential work around to accomplish what you're looking for is to:

1. open the issue you are looking to move from the JSM project to another project in the issue viewer and select the fields that you want copied over.

2. From here, you can export this data into a csv file.

3. Move the issue from the original project to the new destination project, knowing some data won't be copied over (you will be able to restore it via the csv file)

4. Open the issue in the new project

5. Open the csv file and data you exported, and copy the data and enter it into the necessary custom fields in the destination project issue.

Then you should be good to go!

By exporting the data into a csv file, you also have a record of the data that was in each field from the original project. This isn't the most streamlined of processes and is primarily an advantage if you have a lot of fields to map, don't want to lose data, and want a record of the original issue.

Your other option is to mass export lots of issues into a csv file with their data, then import the issues into the destination project as new issues and map the source fields to the destination fields. To take this a step further, you can map the source project issue key with to the Linked Issue field in the destination project during import. This will link the original issue with the newly imported issue. Afterwards you can close out all the issues in the source project.

Hope this helps!

Marcela Junyent_scufs0

Hi,

You can change the field from which the value is copied
Here the manager is set in a custom field Assign to

image (15).png

Regards, Marcela

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud