Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Auto-created tentative appointments lose tentative status on organizer updates (absentCreateStatus not reapplied to unanswered events)

Aperta
  • Qualcosa non va?
#13,504 4 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@kesselb ci sta già lavorando.

Dal 18/8/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

0. to triage bug feature:imip needs info stale
Steps to reproduce
  1. Nextcloud 33.0.2, Mail 5.10, cron working. "Automatically create
    tentative appointments" enabled for the account
    (oc_mail_accounts.imip_create = 1).
  2. Receive an external iMIP invitation (METHOD:REQUEST) and let
    IMipMessageJob process it. The event is created in the calendar and
    rendered as tentative (server writes STATUS:TENTATIVE via
    absentCreateStatus; attendee PARTSTAT remains NEEDS-ACTION). Do not
    respond to the invitation.
  3. Have the organizer modify the event (e.g. change the time), which
    sends an update: a new METHOD:REQUEST with the same UID and a bumped
    SEQUENCE.
  4. Let IMipMessageJob process the update.
Expected behavior

An auto-created event that the user has not yet responded to should
remain visibly tentative after organizer updates (updated details, new
time, but still rendered as tentative). This matches the Outlook
behavior that motivated the feature in #7750.

Actual behavior

The update takes the existing-UID branch in
OC\Calendar\Manager::handleIMip() (lib/private/Calendar/Manager.php,
v33.0.2): the organizer's event data is applied via handleIMipMessage()
WITHOUT reapplying absentCreateStatus. The organizer's copy carries
STATUS:CONFIRMED, which overwrites the locally stamped
STATUS:TENTATIVE. Because the attendee's PARTSTAT is still
NEEDS-ACTION, the event silently flips from rendering as "tentative" to
"did not respond" in the Calendar app — losing exactly the visual cue
the feature exists to provide, without any user action.

Suggested fix: in the existing-UID/update path, when the invitation
was auto-created and the user's PARTSTAT is still NEEDS-ACTION,
reapply the tentative status (or preserve the local STATUS property)
so unanswered auto-created events stay tentative through updates.

Related: #7750, PR #12144, server PR #56924.
Companion issues from the same investigation: https://github.com/nextcloud/server/issues/63333,
https://github.com/nextcloud/mail/issues/13503.

Mail app version

5.10

Nextcloud version

33.0.2

Mailserver or service

No response

Operating system

No response

PHP engine version

None

Nextcloud memory caching

No response

Web server

None

Database

None

Additional info

No response

Lingua principale
JavaScript
Stelle
1k
Fork
348
Merge medio
1g 22h
PR unite (30g)
66

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nextcloud/mail

Tutte le issue di nextcloud/mail

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.