When an automation that has an edit action needs to edit a field value, but this field already has the value that the automation was supposed to add, the automation audit log shows that the issue was edited, but the issue's history doesn't show any update. It makes the status misleading and hard to identify whether it was a problem with the automation rule logic or something else. Adding a new status block in the automation audit log like Issue already has this value would help.