Issue description

The "Send email" automation rule does not send any email on the "Status Changed" event if the previous status has the same "Customer Facing" name as the new status.

Steps to reproduce

1. Create a new workflow that has a transition going from a status called "In progress - L1" a status called "Assigned - L2"
2. Create a new Request Type using an issue type associated to this workflow, click on the "Workflow Statuses" tab, and modify the customer facing status ("status name to show customer") corresponding to "In progress - L1" and "Assigned - L2" to be the same: "In Progress"
   
3. Create a new automation rule that sends an email when the status is changed to "Assigned - L2"
   
4. Create a new Service Desk request using the workflow above
5. Transition the issue from "In progress - L1" to "Assigned - L2"
6. Wait for the customer notification to be sent

Actual Result

The email that should have been triggered by the automation is not sent. Instead, we only see the regular customer notifications that are triggered when the status of an issue is changed:

However, in the automation log, it "looks like" the email should have been sent (although it's not the case):

Expected Result

The email should have been sent from the automation rule, no matter what the previous status was, even if the previous customer facing status was the same, since this is what the automation logs are reporting.

Alternatively, the logs should display a failure instead of a success, with the reason why the email was not sent.

Workaround

Use different names for 2 customer facing statuses: