Skip to end of banner
Go to start of banner

Workflow Post-Functions

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

The JIRA Suite Utilities plugin provides several additional workflow post-functions:

  • Copy Value From Other Field
  • Update Issue Custom Field
  • Clear Field Value

For information on workflow post-functions in JIRA, see the JIRA documentation.

On this page:

Copy Value From Other Field Post-Function

Description

The 'Copy Value From Other Field' post-function copies the value of one field to another field, after a transition has been completed. Either within the very same issue or from parent to sub-task.

Configuration

You must specify the field to copy from, and the field to copy to. For example:

For information on how to configure a post-function in JIRA, see the JIRA documentation.

Example

A workflow is configured so that the 'Resolve' transition has the 'Copy Value From Other Field' post-function. The function is configured to copy the value of the 'Assignee' field to the 'TextField' field. If a user resolves an issue on this workflow, the value of the 'Assignee' field will be copied to the 'TextField' field after the issue is resolved.

Update Issue Custom Field Post-Function

Description

The 'Update Issue Custom Field' post-function updates a custom field to a specified value, after a transition has been completed.

Since version 1.4.10, you may optionally append that value to the field its existing contents, or if the field is allowing multiple values, like a multiple selection field, the option matching the value will be set, without unsetting other options. The same is true for label or version picker custom fields.

Configuration

You must specify the custom field and the desired value. For example:

If you use
%%CURRENT_USER%%
as the custom field value (exactly this, nothing more), the user who triggered the post function will be set as value.

If you use
%%CURRENT_DATETIME%%
as the custom field value (exactly this, nothing more), the current date and time will be set as value.

If you use
%%ADD_CURRENT_USER%%
as the custom field value (exactly this, nothing more), the user who triggered the post function will be appended to the existing field content. Obsolete since 1.4.10, please use append option instead and CURRENT_USER macro.

Additionally for Cascading Select fields, you may either use the value of the option you would like to set, or it's id. In either case, no need to specify the parent option. For example:

  • Vehicles
    • Car
    • Train
    • Bus
  • Buildings
    • House
    • Skyscraper

Using Vehicles as the parameter for Custom Field Value would set the custom field content to that very option. Same if you would choose Train. Or, assuming 10701 is the ID of House, then the option House will be set.


For information on how to configure a post-function in JIRA, see the JIRA documentation.

Example

A workflow is configured so that the 'Start Progress' transition has the 'Update Issue Custom Field' post-function. The function is configured to set the 'Location Select' field to 'Sydney,Australia'. If a user starts progress on an issue on this workflow, the value of the 'Location Select' field will be set to 'Sydney,Australia'.

Clear Field Value Post-Function

Description

The 'Clear Field Value' post-function clears the value of a specified field, after a transition has been completed.

Configuration

You must specify the field to be cleared. For example:

For information on how to configure a post-function in JIRA, see the JIRA documentation.

Example

A workflow is configured so that the 'Close' transition has the 'Clear Field Value' post-function. The function is configured to clear the 'Security Level' field. If a user closes an issue on this workflow, the value of the 'Security Level' field will be cleared.

 

Supported Field Types

JSU supports many different field types such as system fields and custom fields. However you should be aware, that not all field types are supported, and not in all combinations. We aim to cover the most important field types and are continuously adding and improving how different field types are supported. Some custom fields of other third-party apps might never be supported. You should always test anything you do with issue fields with JSU. You can try it with a free 30-day evaluation license.

  • No labels