Page Comparison

...

...

...

...

...

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-task, a linked issue, or an issue within an Epic (during the transition on the Epic).

...

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

Precondition

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 Progress'.

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-task, a linked issue, or an issue within an Epic (during the transition on the Epic).

See Related Issues for more explanation on this topic.

Perform As User

Field Value

Position of the Post Function

...

Instead of using the "Update any Issue Field" post function in the Create transition, you might consider to just configure 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 add the "Store Issue" post function after the "Update Any Issue Field".

Expand
title Example configuration in the 'Create' transition - Click here to expand...
Image RemovedImage Added Note that at in step 4 the "Store Issue" post function is needed, which you have to add manually in the workflow configuration. In our sample 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 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

...

Another example:
A developer has fixed a Bug. He proceeds in the Jira workflow to the status 'Resolved' (this might be triggered from his code pushed to Bitbucket). The 'Update any Issue Field' now adds a the label 'testing-required'.
This would be a very light weight lightweight solution. 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 JIRA, see the JIRA documentation.

Supported Field Types