Issue Summary

Allow administrators to control execution order of validators and post-functions in workflow transitions

Expected Results

• Jira should provide a way to configure or influence the execution order of validators and post-functions on a workflow transition, for example:
Allow certain post-functions to execute before validators on the same transition, or
Introduce a separate type of “post-validation hook” that runs after specific post-functions but can still block or revert the transition if checks fail.
• This would allow the following pattern:
1. Post-function attempts to auto-populate a field.
2. Validator (or post-validation step) checks if the field is populated.
If populated → transition succeeds.
If not populated → transition is blocked or reverted and user is prompted to fill the field.
This would enable more robust workflows where auto-population is the default, and manual input is only required when the automated step fails, instead of always blocking at validator stage.

Actual Results

The workflow transition execution order is fixed:
Conditions
Validators
Post-functions
• The validator always runs before the post-function.
• As a result, the validator fails and blocks the transition even in cases where the post-function would have correctly filled the field.
• There is no way to configure execution order so that the post-function runs first and the validator runs afterward as a fallback.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available