---
title: "Copy value from field to field (Deprecated)"
canonical: "https://support.appfire.com/space/JMWE/461702285/Copy%20value%20from%20field%20to%20field%20(Deprecated)"
format: markdown
---
> Macro (aura-html)

> ℹ️ Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation [here](https://innovalog.atlassian.net/wiki/x/OoCcBQ).

When you add this post-function to a transition and trigger the transition, the add-on copies the value(s) of the selected `Source Field` to the `Destination Field `of the current issue.

### Options

- **Use value before current transition**

Takes the selected `Source Field` value as it was before the transition. This is useful in a case where the user modifies the source field on the **Transition screen **during the transition and you need the field value prior the modification.

- **Return "parent-child" for cascading custom fields**

This option is applicable for **Select list (cascading)** custom fields. If you select the `Return "parent-child" for cascading custom fields` option, values from both the parent and child lists are copied into the destination field. 

For example**, **a custom cascading field has the values `A` and `1` in the parent and its child lists respectively. When this field is copied into a text field

- 
  - without the option, the value `1` is copied into the text field
  - with the option, the value `A-1` is copied into the text field.
- **Ignore empty values**

Will not set (clear) the destination field of the current issue, if the value of the source field is empty or null.

- **Add source value(s) to destination field**

Appends the value(s) of the selected `Source Field` to the `Destination Field` of the current issue. This is applicable only to multi-valued fields.

- **Create missing value(s)**

<span style="color: #000000">Allows automatically creating any missing value(s) while copying values that do not apply to the destination field and hence should be created from the source field. This is applicable only to Affects Version/s, Fix Version/s, Single version and Multi-version picker type custom fields, Components, Radio buttons, Checkboxes, Single select and Multi-select list type custom fields.</span>

### **Conditional execution**

To execute this post-function based on the result of a groovy expression see [Conditional execution/validation using a Groovy expression](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/461996060).

### Error Handling

<span style="color: #333333">By default, all errors (Java Exceptions) raised by this post-function, including those raised by custom Groovy scripts, will be logged in the </span>[JIRA log file](https://confluence.atlassian.com/adminjiraserver073/logging-and-profiling-861253813.html)<span style="color: #333333"> but will not be reported to the user and will not prevent the transition from completing. However, when designing new workflows or troubleshooting them, it is more convenient to be notified immediately of any such error during the execution of the transition. For example on the production Jira instances you might want to show errors </span><span style="color: #333333">*only for the post-function(s) being worked on*</span><span style="color: #333333">, in order to avoid disrupting other workflows. To make errors raised by the </span><span style="color: #333333">*current*</span><span style="color: #333333"> post-function prevent the transition from completing and show the error in the browser, select </span>`Make transition fail when an error occurs in this post-function`<span style="color: #333333">.</span>

<span style="color: #333333">If you want to show all the errors, either </span><span style="color: #333333">*only to the admins *</span><span style="color: #333333">or to</span><span style="color: #333333">* all users*</span><span style="color: #333333">, configure the option globally on the </span><span style="color: #333333">[JMWE configuration page](http://innovalog.atlassian.net/wiki/spaces/JMWE/pages/139627148/JMWE+administration+pages)</span><span style="color: #333333">. For example, on development and staging Jira instances, you can activate error reporting for </span><span style="color: #333333">*all*</span><span style="color: #333333"> JMWE post-functions, to display all the errors and it is recommended to do so, and on production Jira instances you might want to activate error reporting only to administrators so that they can be made aware of configuration errors.</span>

> ⚠️ When the option is selected on a post-function, it overrides the configuration <span style="color: #333333">on the </span><span style="color: #333333">[JMWE configuration page](http://innovalog.atlassian.net/wiki/spaces/JMWE/pages/139627148/JMWE+administration+pages)</span><span style="color: #333333">.</span>