Skip to content
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

[Bug]: Out of office status automation does not set nor reset user status #42138

Closed
4 of 8 tasks
ChristophWurst opened this issue Dec 11, 2023 · 1 comment · Fixed by #42305
Closed
4 of 8 tasks

[Bug]: Out of office status automation does not set nor reset user status #42138

ChristophWurst opened this issue Dec 11, 2023 · 1 comment · Fixed by #42305
Assignees

Comments

@ChristophWurst
Copy link
Member

⚠️ This issue respects the following points: ⚠️

Bug description

I was ooo for a public holiday and tried the out of office feature. The automation did not set my user status to DND and the short message when I left. I manually switched to DND and it was not reset either.

Steps to reproduce

  1. Configure ooo (28 RC2)
  2. Wait until ooo starts (28 RC3)
  3. Look at user status

Bildschirmfoto vom 2023-12-11 08-29-17
Bildschirmfoto vom 2023-12-11 08-28-48

Expected behavior

Status is set to DND when my absence starts.

Installation method

None

Nextcloud Server version

28

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

@ChristophWurst ChristophWurst added bug 1. to develop Accepted and waiting to be taken care of feature: dav feature: status feature: caldav Related to CalDAV internals labels Dec 11, 2023
@ChristophWurst ChristophWurst moved this to 📄 To do (~10 entries) in 💌 📅 👥 Groupware team Dec 11, 2023
@ChristophWurst ChristophWurst added 2. developing Work in progress and removed 1. to develop Accepted and waiting to be taken care of labels Dec 11, 2023
@ChristophWurst ChristophWurst moved this from 📄 To do (~10 entries) to 🏗️ In progress in 💌 📅 👥 Groupware team Dec 11, 2023
@miaulalala
Copy link
Contributor

Figured it out. The implementation of

public function scheduleAfter(string $job, int $runAfter, $argument = null): void;

does not update the last_run timestamp, only the last_checked when the job already exists. That means if an earlier run has set the last_run timestamp to a timestamp in the future, the run will not happen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

3 participants