Clear Field Value Post Function

 

JSU for Jira Server/Data Center

This is the JSU for Jira Server/Data Center documentation. If you are using JSU on Jira Cloud, see our JSU Cloud documentation.

Description

The 'Clear Field Value' post function clears the value of a specified field on one or more issues after a transition is complete.

Configuration

Example configuration of the Clear Field Value post function.


Precondition

If you are using preconditions with a JSU post function, you can use the following options to define how the precondition is evaluated:

  • Ignore precondition (default): Every precondition is ignored which means that the post function will always be performed

  • True: Precondition must be true to execute a post function

  • False: Precondition must be false to execute a post function

Learn more about JSU preconditions in Workflow Preconditions.

Issue relation

The field can be on the issue in transition(within the same issue) or a related issue, like a subtask, a linked issue, an issue within an Epic (during the transition on the Epic), or the result of a JQL query.

See Related Issues for more details on each option.

Perform As User

Field

You must specify the field to be cleared on the related issues, for example, Fix Version.

Position of the post function

Jira transitions include essential post functions that are executed in a specific order. When adding JSU post functions to a transition it is important to position the post function with respect to the essential post functions.

‘Create’ transition

The ‘Create' transition is an issue’s first transition and does not have a source status (only destination status - usually Open). If you add the ‘Clear Field Value’ post function to the ‘Create’ transition, you should position it before Jira’s 'Create the issue originally' post function except when clearing labels that need to be cleared after the issue has been created.

Any other transition (not ‘Create’)

Position the ‘Clear Field Value’ post function anywhere before the ‘Update change history for an issue and store the issue in the database’ post function.

Supported field types