-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(userstatus): Fix user status automation in real-life scenario #46077
Conversation
/backport to stable29 |
6540e12
to
3402d98
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks legit. Tested with meeting / OOO and call / OOO
3402d98
to
ec5466d
Compare
Order of applying: - Out-of-office - Availability - Call - Meeting - User status Signed-off-by: Joas Schilling <coding@schilljs.com>
ec5466d
to
2c977d2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feels a bit like the rules for https://www.ultra-watten.com/watten-regeln ahahaha
Nice one, thanks for fixing that
Steps
oc_user_status
(See backup status of 1 and live status of 2)oc_user_status
(See backup status of 1 and live status DND of 5)oc_user_status
(See backup status of 1 and live status of 2)If you replace step 2 with doing a call, it worked already.
Also tested with OOO and that one also failed to overwrite the meeting status.
Checklist