[Bug]: Automated status overwrites manually set status

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

Tested in latest c.nc.com

Even if it is a calendar example, I think the general status handling happens on the server. If I'm wrong, feel free to move the ticket to the repository it belong to.

Automated status, set from the calendar overwrites my manually set status.

Example use case: I set a "out of office" status during vacation. But during working time, when there is a appointment in my calendar, the status shows "in a meeting", no hint that I'm on vacation:

Steps to reproduce

1. Set your own status
2. Wait until a automated status kick-in (e.g. a meeting starts according to your calendar)
3. check your status

Expected behavior

Custom set status should be prioritized over automatically set status.

If I state explicitly that I'm out of office, traveling or whatever, than this is should be more important than any automatically detected states. Also if I join a call while being on vacation, or traveling it is still more important to know my personal status and not the system status.

Installation method

None

Nextcloud Server version

26

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

No files, tests, or entry points are named. Reproduce the issue by setting a manual status, starting a calendar event, and checking the resulting status; then trace the server-side handling of manual and automated statuses. Done means an explicitly set status remains visible when an automated calendar status is triggered.