🚀Edit Work Post Function
The Edit Work post function allows you to automatically modify issue fields during a workflow transition.
Overview
With Edit Work, you can:
Edit multiple fields in an issue during a workflow transition.
Apply changes only when specific preconditions are met.
Change the Actor who performs the changes.
Copy one field to another within the same issue.
Copy field values from the parent issue, up to two levels up in the hierarchy.

Settings
Actor
Defines who is recorded as having made the changes:
User who transitioned the issue (default)
Workflow Building Blocks for Jira (app actor)
The selected actor will appear in the issue’s change history.
User who transitioned the issue – Recommended for most cases; changes are attributed to the actual user.
Workflow Building Blocks for Jira – Has all permissions needed to evaluate preconditions and edit the issue. Recommended for complex scenarios where permission checks might prevent changes from being applied.
Preconditions
Preconditions control whether the post function runs.
Configure preconditions using the condition builder known from the Ultimate Validator.
The builder generates a Jira expression, evaluated as the selected Actor.
The post function runs only if the precondition evaluates to
true
.
Current User option in preconditions
Always represents the actual user who performed the transition, regardless of the Actor setting.
Permission Requirements
To see groups other users belong to: Administer Jira global permission is required.
To see roles of other users: Administer Projects permission for the project, or Administer Jira global permission is required.
Choose Fields
The Edit Work post function supports editing the following Jira fields:
Text & Selection Fields
All text fields, standard select lists (single and multi-select), radio buttons, checkboxes, URL fields, number fields
User & Group Fields
User picker, team picker, group picker
Issue Metadata
Issue type, priority, resolution, parent, labels, components, project picker
Time Tracking
Original estimate, remaining estimate
Versions & Dates
Version pickers, date fields
Agile
Sprint
Jira Service Management Fields
Request type, request participants, organisations
Order of Post Functions
Post functions perform additional processing after a workflow transition is executed.
When multiple post functions are added to the same transition, the execution order is not guaranteed.
Our post functions always operate on the current data at the time they run, including when evaluating preconditions. If multiple post functions modify the same fields and those fields are referenced in preconditions, the results may vary due to the asynchronous nature of post function execution.
Last updated