SLA update time overrules ticket escalation if first response is higher

[MrGeneration]

Used Zammad Version

6.3.1

Environment

• Installation method: 6.3.x.70297fbb6.saas
• Operating system (if you're unsure: cat /etc/os-release ): any
• Database + version: any
• Elasticsearch version: any
• Browser + version: verified on Vivaldi 6.7.3329.29
• This issue has been found by our community: https://community.zammad.org/t/sla-update-escalation-time-calculate-on-ticket-creation/13548

Actual behaviour

The update time overrules the first response time if the update time is chosen smaller than the first response time.
This draws the "need" of a first response time kind of useless.

Our documentation however states this:

(https://admin-docs.zammad.org/en/latest/manage/slas/how-do-they-work.html)

Expected behaviour

First response time is not being overruled by update time as long as no first response has occured.

Steps to reproduce the behaviour

• Configure an SLA like so
  
• Send an email to your instance that fits your SLA and check the sla timings in the history.

Support Ticket

No response

I'm sure this is a bug and no feature request or a general question.

yes