Page Comparison

Description

The ' Update any Issue Field ' post - function updates any field to a specified value after a transition has been completed. This can be a system- or a custom field. The field can be on the issue in transition(within the same issue) or on a related issue, like a sub-tasksubtask, a linked issue, or an issue within an Epic (during the transition on the Epic). In addition to setting values to fields, the ' Update any Issue Field ' post - function can also add comments.

...

We use the Update any Issue Field post function like this in the 'Start Progress' transition of our Story issue types. If the Story is part of an Epic, the Epic Status will be set to '

In the past users forgot to change the Epic Status in time and it was left behind as 'To Do'. Using JSU this does no more happen.

Update field on all issues related as

The field can be on the issue in transition(within the same issue) or on a related issue, like a sub-tasksubtask, a linked issue, or an issue within an Epic (during the transition on the Epic).

See Related Issues for more explanation on this topic.

...

It is important to place the post function in the correct order of other post functions.

Create Transition

 The 'The Create' transition is the very first transition, which does not yet has have a source status (only destination status - usually Open, but could also be another). Instead of using the "Update the Update any Issue Field " post function in the Create transition, you might consider just configuring a default value for that field.

If you are using the " Update any Issue Field " post function in the Create transition, you must put it after the "Creates the issue originally." but before the "Re-index an issue to keep indexes in sync with the database." post function. Depending on the field type, you also need to must add the "Store Issue " post function after the "Update the Update Any Issue Field".

Expand
title Example configuration in the 'Create' transition - Click here to expand...
Note that in In step 4 the "Store Issue" post function is needed, which you have to must add manually in the workflow configuration. In our example, we also use a Workflow Precondition before the " Update any Issue Field " post function. This just makes it a more interesting 'real-life' example.

Any other Transition (not Create)

Put Use the " Update any Issue Field " post function anywhere before the " Update change history for an issue and store the issue in the database ." post function

...

Examples

• See the above example of a Story changing the Epic Status of its Epic.

...

• Or, whenever a parent issue is set to

...

• Status
  colour Blue title In Progress

...

• , the assignee of all its

...

• subtasks could be set to the current user (the one changing the status on the parent).

...

• A developer

...

• fixes a bug and proceeds in the Jira workflow to the

...

• Status
  colour Green title Resolved

  status (this might be triggered from his code pushed to Bitbucket). The 'Update any Issue Field' now adds the label 'testing-required'.
  

...

• There are also cases when you need a more complex solution. Have a look at Testing and Fixing Bugs.

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

Supported Field Types

...