---
title: "Clear field value of linked issues"
canonical: "https://support.appfire.com/space/JMWE/78054003/Clear%20field%20value%20of%20linked%20issues"
format: markdown
---
Are you using JMWE for Cloud and want to learn how to use this post-function? Head to our documentation  here . Documentation for   is available  here . A workflow post-function that clears the value of the selected field(s) of the issues linked to the current issue through a specific link type. To add the 'Clear field value of linked issues' 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 Functions  in the properties panel. Click on  Add  post function . Select  Clear field value of linked issues  from the list of post-functions. Click on  Add  to add the post-function on the transition. Choose the field(s) that should be cleared from  Fields. Select the link from the  Issue Link  drop-down, or leave it as  Any  for any link type other than Issue/Subtask, Epic/Story and Jira Portfolio hierarchy Click on  Add  to add the post-function to the transition. Related links : For information on where the post-function needs to be placed on a transition, see  Placing post-functions on a transition . Refer to the  Use cases for post-functions  page for use cases for this post-function. When you add this post-function to a transition and trigger it, the add-on clears the selected field(s) of the issues linked to the current issue through the specified link type. "Relates to" link type Beware of the default "relates to" link type, which can cause confusion. The problem stems from the fact that "relates to" is both the  inward   direction  and the  outward direction  of the "Relates" link type. We recommend that you rename one of the directions to "is related to" to avoid confusion. This can be done on the Issue Linking Jira admin page. Run as Run as user Any user specified in this field will be the author of the action performed by the post-function. Leave it blank for the current user to be the author. Conditional execution To execute this post-function based on the result of a groovy expression see  Conditional execution/validation using a Groovy expression . 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,  o n   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. When the option is selected on a post-function, it overrides the configuration  on the  JMWE configuration page .