Describe your issue

On creating a new task, two values are being assigned (IMHO) incorrectly; start:now AND priority:M

Start: value is being treated a duplicate of entry: value, and that's not what that attribute is for. No value should be assigned until a user starts the task.

Assigning priority:M default leaves one value up and two down, and that ain't right! ;-) Unless a user assigns a user priority, the default should be pri:nul.

Related is work on #384, and the idea that a pri:L should have a lower urgency coefficient than pri:X, as described in #410

Steps to reproduce

Stop assigning default values to start: and priority: when adding a new task.

What was the expected result?

No response

Put here any screenshots or videos (optional)

No response

How can we contact you (optional)

No response

Would you like to work on this issue?

None

By submitting this issue, I have confirmed that:

• I have starred the repo ⭐ and watched 👀 it on GitHub and followed the contribution guidelines.