---
title: "Copy field value to parent issue"
canonical: "https://support.appfire.com/space/JMWE/461406774/Copy%20field%20value%20to%20parent%20issue"
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://appfire.atlassian.net/wiki/x/6IetB).

When you add this post-function to a transition and trigger the transition, the add-on copies the value(s) of the selected field to the same field of the issue's parent issue. 

### Options 

- **Ignore empty values**

Will not set (clear) the selected field of the parent issue, if the value from the current issue is empty or null.

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

Appends the value(s) of the selected field to the same field of the issue's parent issue. This is applicable only to multi-valued fields.

### **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).

> ℹ️ The parent/child relationship in Jira refers to issues and their subtasks, not to the Epics and their Stories. 
> ℹ️ 
> ℹ️ If you wish to copy a field from a **Story** to an **Epic**, you should use the [Copy field value from linked issue](https://appfire.atlassian.net/wiki/spaces/JMWE/pages/78056400) post-function.

### 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>