---
title: "Copy a custom field value to another field"
canonical: "https://support.appfire.com/space/CSOT/68748800/Copy%20a%20custom%20field%20value%20to%20another%20field"
format: markdown
---
> Macro (aura-html)

# Overview

Create on Transition for Jira offers two ways to copy a custom field value to a different custom field. The new way provides the ability to do this for more fields than before.

For this example, let's say you want to copy the value of **source_cf** to **target_cf** for the newly created issue of the subtask.

## Best practice

### Use "Set custom field"

This is the easiest approach provided you have enough **Set custom field** slots to use for your needs.

## Steps

<span style="color: #333333">The following steps demonstrate how to configure Create on Transition for Jira for copying a custom field value to another field:</span>

|  |  |  |
| --- | --- | --- |
| ![image](media://8ad2b093-c56a-4eb2-a36a-347ac4a797f5) | ## Step 1<br>As a Jira Administrator or Workflow Administrator:<br>1. Click the **Cog** icon to open the *Settings* menu and select **Issues**
2. Click **Workflows**
3. Navigate to your workflow and edit your workflow to create a draft version.
4. Select the transition
5. Select the *Post Functions* tab.
6. Click* Add post function*
7. Select *Update issues (Bob Swift)* post function and add.
  1. Note: This is applicable to *Create Sub-task (Bob Swift) and Create Sub-task (Bob Swift) *post functions as well. | ![image]() |
| ![image](media://fa51c13a-57e6-410c-bce6-14d2bc945ef0) | ## Step 2<br>1. Select the *Custom fields* tab.
2. Click *+Add custom field*
3. Select the respective custom field from the list, **target_cf** in this example.
4. Use the [substitution variable syntax](https://appfire.atlassian.net/wiki/spaces/CSOT/pages/68749234) to specify the second field (value field). **%original_source_cf%** in this example.
5. Click the **Add** button to save your configuration. | ![image](media://345abfa4-623d-4d87-913c-037e8f07c164) |
| ![image](media://823e8adb-5cc2-492d-bb9a-e321e9dc6bc2) | ## Step 3<br>1. Ensure to publish your workflow. It is always recommended to save a backup of the previous workflow when prompted.
2. Create an issue of type "Story".
3. Validate that the new sub-task issues were created and that it contains the name prepended before the parent summary. |  |

### Use "Copy parent or original issue custom fields"

These fields normally just list custom fields you wish to copy to the new issue. This is the best way to copy fields exactly to the newly created issue. As many fields as you like can be copied this way. This is useful when you have a significant number of fields to copy.

## Steps

<span style="color: #333333">The following steps demonstrate how to configure Create on Transition for Jira for copying a custom field value to another field:</span>

|  |  |  |
| --- | --- | --- |
| ![image](media://8ad2b093-c56a-4eb2-a36a-347ac4a797f5) | ## Step 1<br>As a Jira Administrator or Workflow Administrator:<br>1. Click the **Cog** icon to open the *Settings* menu and select **Issues**
2. Click **Workflows**
3. Navigate to your workflow and edit your workflow to create a draft version.
4. Select the transition
5. Select the *Post Functions* tab.
6. Click* Add post function*
7. Select *Update issues (Bob Swift)* post function and add.
  1. Note: This is applicable to *Create Sub-task (Bob Swift) and Create Sub-task (Bob Swift) *post functions as well. | ![image]() |
| ![image](media://fa51c13a-57e6-410c-bce6-14d2bc945ef0) | ## Step 2<br>1. Select the *Custom fields* tab.
2. Choose either the **Copy parent issue custom fields** or the **Copy original issue custom fields** parameter appropriate for your scenario.
3. Select the respective custom fields from the list that you wish to copy
4. Click the **Add** button to save your configuration. | ![image](media://a2f1ee07-cae3-4e99-8d5c-0de06ca7caed) |
| ![image](media://823e8adb-5cc2-492d-bb9a-e321e9dc6bc2) | ## Step 3<br>1. Ensure to publish your workflow. It is always recommended to save a backup of the previous workflow when prompted.
2. Create an issue of type "Story".
3. Validate that the new sub-task issues were created and that it contains the name prepended before the parent summary. |  |