Issue Summary

In the new UI/navigation the issue history has events batched rather than creating one for single change made in a time frame:

Currently the time stamp of changes might not align when it comes to updates made by other applications, such as Automation for Jira.

Steps to Reproduce

• Create a rule whose trigger is Field value changed
  • In my example I used the field Priority as the source
  • I also set the rule to transition the issue to In progress when that happens
• Perform a change to the field the rule is listening to, but also quickly change other fields along with it

Expected Results

From the user's perspective the Automation rule will trigger after the field value changes, hence the Automation related history entry will be displayed after the entry that shows the value being changed in the source field.

Actual Results

In this case the Automation rule's change might be logged before the change to the source field:

Workaround

No workaround at the moment.