can't escape date parsing in task titles #2589

Open
opened 2026-03-22 14:13:48 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @probecat on GitHub (Mar 11, 2026).

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

When a task title naturally contains a date-like phrase, QAM parses it as a due date with no way to opt out.

Example:

delete mails up to january 30th

This sets a due date of January 30th, which is unintended.

Proposed solution:
Support an escape syntax to suppress date (and ideally other fields) parsing in the title. Possibly:

"delete mails up to january 30th" - quoted content is treated as literal text

Todoist handles this with quoted strings, too. So this would be consistent for Todoist mode at minimum, but ideally both modes.

Vikunja Version

v2.1.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @probecat on GitHub (Mar 11, 2026). ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description When a task title naturally contains a date-like phrase, QAM parses it as a due date with no way to opt out. **Example:** > `delete mails up to january 30th` This sets a due date of January 30th, which is unintended. **Proposed solution:** Support an escape syntax to suppress date (and ideally other fields) parsing in the title. Possibly: `"delete mails up to january 30th"` - quoted content is treated as literal text Todoist handles this with quoted strings, too. So this would be consistent for Todoist mode at minimum, but ideally both modes. ### Vikunja Version v2.1.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
Author
Owner

@probecat commented on GitHub (Mar 11, 2026):

Addendum: It seems adding double quotes around the date itself escapes date parsing.

Example:

don't parse "tomorrow"

…seems to work. Though, quotes are preserved in task title; minor aesthetic hindrance.

Requesting to document this behavior if this was a deliberate choice.

@probecat commented on GitHub (Mar 11, 2026): **Addendum:** It seems adding double quotes around the date itself escapes date parsing. **Example:** > `don't parse "tomorrow"` …seems to work. Though, quotes are preserved in task title; minor aesthetic hindrance. Requesting to document this behavior if this was a deliberate choice.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2589