| Info |
|---|
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation here. |
| Excerpt |
|---|
A workflow post-function that sets the value(s) of a selected field with value(s) from the same field of an issue's parent issue. |
To add the 'Copy field value from parent issue' post-function to a transition:
Click Edit for the workflow that has the transition you wish to configure the post-function on.
In the Workflow Designer, select the transition.
Click on
Post
Functionsin the properties panel.Click on
Addpost function.Select
Copy field value from parent issuefrom the list of post-functions.Click on
Add
to add the post-function on the transition.
Select the field from the
Fielddrop-down.Select the options provided to add required parameters.
Click on
Addto add the post-function to the transition.
| Note |
|---|
Note that you should publish the workflow |
| Panel |
|---|
Related links : |
When you add this post-function to a transition and trigger the transition, the add-on sets the value(s) of the selected field to the value(s) from the same field of the issue's parent issue.
Options
Copy only if not set
Copies the value of the selected field, only when the field is
empty on the current issue.
Ignore empty values
Will not set (clear) the selected field of the current issue, if the value from the parent issue is empty or null.
Add source value(s) to destination field
Appends the selected field of the current issue with value(s) from the same field of its 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.
| Info |
|---|
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 an Epic to a Stories, you can use the Copy field value to |
related issues post-function. |
Error Handling
By default, all errors (Java Exceptions) raised by this post-function, including those raised by custom Groovy scripts, will be logged in the JIRA log file 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
only for the post-function(s) being worked on, in order to avoid disrupting other workflows.
To make errors raised by the current post-
function prevent the transition from completing and show the error in the browser, select Make transition fail when an error occurs in this post-function.
If you want to show all the errors, either only to the admins or to all users, configure the option globally on the JMWE configuration page. For example, on development and staging Jira instances, you can activate error reporting for all 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.
| Note |
|---|
When the option is selected on a post-function, it overrides the configuration on the JMWE configuration page. |