Skip to content

Title format preview: date and time examplars are ambiguous #4028

@andihindle

Description

@andihindle

In Preferences > General > New Note Defaults > Title Format, if you select 'Custom Format', the preview shown appears to use the current (user-machine-local; hereinafter 'zulu') date and time: this is unclear, and can cause confusion as a result. For example: adjusting these settings prior to making this report, my local date and time is the 1st of November, 10:39 am. Using this is the preview creates confusion unless it is clear that the user-machine-local time is being used because:

  1. the 1st of November when presented as (for example, YYYY-MM-DD) as "2025-11-01" could equally be interpreted as the the 11th of January 2025 : in other words, it leads to a lack of clarity because the 'day' value is ambiguous.

  2. If zulu time is in the morning, then selecting a 24-hour time doesn't cause a change (which is confusing, because it's hard to be sure that time format selected is behaving correctly). If zulu time is in the morning and after 10am, then the time format does not show a leading zero for the relevant formats. (There will be other similar examples depending on the combination of selected time format and zulu time)

The easiest solution would be to put additional explanatory language in the preview; for example: "Preview (based on current date/time):"

Other approaches exist (for example: using a fixed but unambiguous date (say, January 31st, 2025); using several different time options appropriate to the format, for example: 22:14 (for HH:MM), 9:57am (which would work for both h:mm and hh:mm, when it would be displayed at 09:57am). A more complex approach like this would have the benefit that the user could be more certain that they had correctly selected their desired format; but would take longer to code and is more open to potential errors. Or, potentially, offering the user the option to enter their own sample date/time to test. However, I'm not convinced that any of these options are well-aligned with the longevity manifesto. I do, however, consider that adding the simple explanatory text as described above would improve the user experience with minimal-to-no impact on long-term maintainability.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions