Open Bug 2061232 Opened 3 months ago Updated 1 month ago

Load create-mode date/time defaults

Categories

(Calendar :: Calendar Frontend, task)

task
Points:
3

Tracking

(Not tracked)

People

(Reporter: arschmitz, Unassigned)

References

(Depends on 1 open bug, Blocks 5 open bugs)

Details

(Whiteboard: [calendar-ui-create-edit])

Summary:
Set the initial dates and times when the user creates an event. Use where the
user clicked or the New Event action to choose the starting values.

Put these values in the draft, which holds unsaved changes. Do not create an
event until Save.

Links:

Open decision:

  • Zeplin says New Event starts one hour from now and lasts 30 minutes. The
    interaction guide previously said to start with an all-day event.
    Product/design must confirm which rule to use before implementation.

Acceptance criteria:

  • When creation starts from a calendar click, use that click's date and time.
  • For New Event, use the current date and time plus one hour, with a 30-minute
    duration for a timed event, subject to the decision above.
  • Record and apply the agreed All-day or timed default.
  • Set defaults only for the current new event, after its blank draft is ready.
  • Starting another event, changing the dialog's target, or closing it prevents
    the earlier default result from changing the draft.
  • Finish applying defaults, or report their failure, before the dialog's
    readiness check completes. Initial values must not cause growth after positioning.
  • Setting defaults or entering values must not create or change a saved event.

Required implementation details:

  • Keep default-selection rules in this date/time feature. The shared draft
    model receives the chosen values; it does not choose them.
  • Send a date/time-only draft update with serializable values: plain date/time
    data, All-day state, and timezone IDs. Keep calIDateTime, live calendar
    objects, input elements, and other live platform objects out of Redux.
  • Render the current draft through stable storeObserver selections. Do not
    add getters that read the store directly.
  • A session identifies one create or edit operation. Check that each default
    result belongs to the current session before applying it.

Minimum test coverage:

  • Check calendar-click values, New Event values, and the 30-minute duration.
  • Check the agreed All-day or timed default and date/time-only draft updates.
  • Check that Redux contains no live platform objects.
  • Start event B before defaults for A finish, and check that A cannot change B.
    Also check closing the dialog before defaults finish.
  • Check that defaults finish or fail before show readiness completes.
  • Check that no event is created or changed before Save.
  • Run axe checks on the displayed create states where supported.

Out of scope:

  • Implementing the shared draft model or loading existing event values.
  • Date picker, time entry, timezone selection, and control visibility/enabling.
  • Required-field and date-range validation, event creation, and saving.
Blocks: 2061240
Blocks: 2061244
Blocks: 2061579
Blocks: 2062086
Blocks: 2061214

TB-Tools story description:

Summary:
Set the initial dates and times when the user creates an event. Use where the
user clicked or the New Event action to choose the starting values.

Put these values in the draft, which holds unsaved changes. Do not create an
event until Save.

Links:

Acceptance criteria:

  • When creation starts from a calendar click, use that click's date and time.
  • For New Event, use the current date and time plus one hour, with a 30-minute
    duration for a timed event, subject to the decision above.
  • Record and apply the agreed All-day or timed default.
  • Set defaults only for the current new event, after its blank draft is ready.
  • Starting another event, changing the dialog's target, or closing it prevents
    the earlier default result from changing the draft.
  • Finish applying defaults, or report their failure, before the dialog's
    readiness check completes. Initial values must not cause growth after positioning.
  • Setting defaults or entering values must not create or change a saved event.

Required implementation details:

  • Keep default-selection rules in this date/time feature. The shared draft
    model receives the chosen values; it does not choose them.
  • Send a date/time-only draft update with serializable values: plain date/time
    data, All-day state, and timezone IDs. Keep calIDateTime, live calendar
    objects, input elements, and other live platform objects out of Redux.
  • Render the current draft through stable storeObserver selections. Do not
    add getters that read the store directly.
  • A session identifies one create or edit operation. Check that each default
    result belongs to the current session before applying it.

Minimum test coverage:

  • Check calendar-click values, New Event values, and the 30-minute duration.
  • Check the agreed All-day or timed default and date/time-only draft updates.
  • Check that Redux contains no live platform objects.
  • Start event B before defaults for A finish, and check that A cannot change B.
    Also check closing the dialog before defaults finish.
  • Check that defaults finish or fail before show readiness completes.
  • Check that no event is created or changed before Save.
  • Run axe checks on the displayed create states where supported.

Out of scope:

  • Implementing the shared draft model or loading existing event values.
  • Date picker, time entry, timezone selection, and control visibility/enabling.
  • Required-field and date-range validation, event creation, and saving.
Points: --- → 3

TB-Tools story description:

Summary:
Set the initial dates and times when the user creates an event. Use where the
user clicked or the New Event action to choose the starting values.

Put these values in the draft, which holds unsaved changes. Do not create an
event until Save.

Links:

Acceptance criteria:

  • When creation starts from a calendar click, use the date and / or time from the passed in data if it exists.
  • For New Event, use either the passed in data or the current date and time plus one
    hour, with a 30-minute duration for a timed event, should round to next 15 minutes.
  • Record and apply the agreed All-day or timed default.
  • Set defaults only for the current new event, after its blank draft is ready.
  • Starting another event, changing the dialog's target, or closing it prevents
    the earlier default result from changing the draft.
  • Finish applying defaults, or report their failure, before the dialog's
    readiness check completes. Initial values must not cause growth after positioning.
  • Setting defaults or entering values must not create or change a saved event.

Required implementation details:

  • Keep default-selection rules in this date/time feature. The shared draft
    model receives the chosen values; it does not choose them.
  • Send a date/time-only draft update with serializable values: plain date/time
    data, All-day state, and timezone IDs. Keep calIDateTime, live calendar
    objects, input elements, and other live platform objects out of Redux.
  • Render the current draft through stable storeObserver selections. Do not
    add getters that read the store directly.
  • A session identifies one create or edit operation. Check that each default
    result belongs to the current session before applying it.

Minimum test coverage:

  • Check calendar-click values, New Event values, and the 30-minute duration.
  • Check the agreed All-day or timed default and date/time-only draft updates.
  • Check that Redux contains no live platform objects.
  • Start event B before defaults for A finish, and check that A cannot change B.
    Also check closing the dialog before defaults finish.
  • Check that defaults finish or fail before show readiness completes.
  • Check that no event is created or changed before Save.
  • Run axe checks on the displayed create states where supported.

Out of scope:

  • Implementing the shared draft model or loading existing event values.
  • Date picker, time entry, timezone selection, and control visibility/enabling.
  • Required-field and date-range validation, event creation, and saving.

TB-Tools story description:

Summary:
Set the initial dates and times when the user creates an event. Use where the
user clicked or the New Event action to choose the starting values.

Put these values in the draft, which holds unsaved changes. Do not create an
event until Save.

Links:

Acceptance criteria:

  • When creation starts from a calendar click, use the date and / or time from the passed in data if it exists.
  • For New Event, use either the passed in data or the current date and time starting at the next 30min interval, with a 30-minute duration for a timed event, should round to next 15 minutes.
  • Record and apply the agreed All-day or timed default.
  • Set defaults only for the current new event, after its blank draft is ready.
  • Starting another event, changing the dialog's target, or closing it prevents
    the earlier default result from changing the draft.
  • Finish applying defaults, or report their failure, before the dialog's
    readiness check completes. Initial values must not cause growth after positioning.
  • Setting defaults or entering values must not create or change a saved event.

Required implementation details:

  • Keep default-selection rules in this date/time feature. The shared draft
    model receives the chosen values; it does not choose them.
  • Send a date/time-only draft update with serializable values: plain date/time
    data, All-day state, and timezone IDs. Keep calIDateTime, live calendar
    objects, input elements, and other live platform objects out of Redux.
  • Render the current draft through stable storeObserver selections. Do not
    add getters that read the store directly.
  • A session identifies one create or edit operation. Check that each default
    result belongs to the current session before applying it.

Minimum test coverage:

  • Check calendar-click values, New Event values, and the 30-minute duration.
  • Check the agreed All-day or timed default and date/time-only draft updates.
  • Check that Redux contains no live platform objects.
  • Start event B before defaults for A finish, and check that A cannot change B.
    Also check closing the dialog before defaults finish.
  • Check that defaults finish or fail before show readiness completes.
  • Check that no event is created or changed before Save.
  • Run axe checks on the displayed create states where supported.

Out of scope:

  • Implementing the shared draft model or loading existing event values.
  • Date picker, time entry, timezone selection, and control visibility/enabling.
  • Required-field and date-range validation, event creation, and saving.

TB-Tools story description:

Summary:
Set the initial dates and times when the user creates an event. Use where the
user clicked or the New Event action to choose the starting values.

Put these values in the draft, which holds unsaved changes. Do not create an
event until Save.

Links:

Acceptance criteria:

  • When creation starts from a calendar click, use the date and / or time from the passed in data if it exists.
  • For New Event, use either the passed in data or the current date and time starting at the next 30min interval, with a 30-minute duration for a timed event.
  • Record and apply the agreed All-day or timed default.
  • Set defaults only for the current new event, after its blank draft is ready.
  • Starting another event, changing the dialog's target, or closing it prevents
    the earlier default result from changing the draft.
  • Finish applying defaults, or report their failure, before the dialog's
    readiness check completes. Initial values must not cause growth after positioning.
  • Setting defaults or entering values must not create or change a saved event.

Required implementation details:

  • Keep default-selection rules in this date/time feature. The shared draft
    model receives the chosen values; it does not choose them.
  • Send a date/time-only draft update with serializable values: plain date/time
    data, All-day state, and timezone IDs. Keep calIDateTime, live calendar
    objects, input elements, and other live platform objects out of Redux.
  • Render the current draft through stable storeObserver selections. Do not
    add getters that read the store directly.
  • A session identifies one create or edit operation. Check that each default
    result belongs to the current session before applying it.

Minimum test coverage:

  • Check calendar-click values, New Event values, and the 30-minute duration.
  • Check the agreed All-day or timed default and date/time-only draft updates.
  • Check that Redux contains no live platform objects.
  • Start event B before defaults for A finish, and check that A cannot change B.
    Also check closing the dialog before defaults finish.
  • Check that defaults finish or fail before show readiness completes.
  • Check that no event is created or changed before Save.
  • Run axe checks on the displayed create states where supported.

Out of scope:

  • Implementing the shared draft model or loading existing event values.
  • Date picker, time entry, timezone selection, and control visibility/enabling.
  • Required-field and date-range validation, event creation, and saving.
Type: enhancement → task
You need to log in before you can comment on or make changes to this bug.