The Field changed event trigger executes a rule when a specified field is updated according to the configuration.
The field to be evaluated can be chosen from most systems and custom fields in the Jira instance.
Field changed event configuration
Below you will find a detailed description of each parameter of the basic configuration of the trigger.
Field*
Select the field that should be checked for changes. Only changes to this field will trigger the rule.
Start typing the field name for quicker selection.
Changed to*
Further refine which type of field change should trigger the rule. You can choose among these options:
Value*
Select an exact field value. Only when the field changes to this exact value it will trigger the rule.
This option is only available if the Changed to parameter is set to Selected value.
Use cases
Use case | Automated action | Use case description | Complexity |
---|---|---|---|
Notify the project lead on priority changes | When the priority is changed to "Blocker", a comment will be added with a user mention alerting the project lead. | BEGINNER | |
Sum up value in parent issue on field change in sub-tasks | Calculate field values from all sub-tasks and writes the sum into a corresponding field in the parent issue. | INTERMEDIATE | |
Keep the priority of parents and sub-tasks in sync | When the priority of a parent issue is updated, all sub-tasks will be updated accordingly. | BEGINNER | |
Transition issues when assigned to a developer | Transition issue | When the assignee is changed to a user in the "Developers" project role, the issue is transitioned to IN DEVELOPMENT. | BEGINNER |
Resolve issues when all options of a checklist are checked | When all options of a custom checkbox field are ticked, the issue is resolved and transitioned to DONE | INTERMEDIATE |
If you still have questions, feel free to refer to our support team.