Date field defaults to today's date with a clear button #63

Open
opened 2026-07-26 18:21:29 +02:00 by cloudbot · 0 comments
Collaborator

Goal

When an entry form renders a template's Date field, it should default to
today's date instead of being blank, and provide a clear affordance so the
user can blank it out again if they don't want a date recorded.

Motivation

Most entries logged on a given day are for that day, so requiring the
user to open the date picker and select today's date every time is
unnecessary friction. Occasionally a date isn't wanted at all, so clearing
needs to stay possible.

Acceptance criteria

  • A new entry with a Date field pre-populates that field with today's
    date (no tap required).
  • The Date field shows a clear affordance (e.g. an icon/button) that
    blanks the field back to empty/unset.
  • Opening the date picker still works as before and still seeds from
    today when the field is currently blank.
  • Editing an existing entry does not overwrite an already-set (or
    already-cleared) date with today's date — the default only applies
    to a fresh/blank field.

Non-goals / constraints

  • Not changing TimeInput, even though it has the same lack of a clear
    affordance today — out of scope unless the user wants it bundled in.

None

## Goal When an entry form renders a template's Date field, it should default to today's date instead of being blank, and provide a clear affordance so the user can blank it out again if they don't want a date recorded. ## Motivation Most entries logged on a given day are *for* that day, so requiring the user to open the date picker and select today's date every time is unnecessary friction. Occasionally a date isn't wanted at all, so clearing needs to stay possible. ## Acceptance criteria - [ ] A new entry with a Date field pre-populates that field with today's date (no tap required). - [ ] The Date field shows a clear affordance (e.g. an icon/button) that blanks the field back to empty/unset. - [ ] Opening the date picker still works as before and still seeds from today when the field is currently blank. - [ ] Editing an existing entry does not overwrite an already-set (or already-cleared) date with today's date — the default only applies to a fresh/blank field. ## Non-goals / constraints - Not changing `TimeInput`, even though it has the same lack of a clear affordance today — out of scope unless the user wants it bundled in. ## Related None
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
utilities/Logbook#63
No description provided.