[Feature request] Set options like due date while adding
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 706
- Forks
- 117
- Avg merge
- 8h 50m
- Merged PRs (30d)
- 18
Description
I think it would be very nice to be able to set additional options for a task while adding it.
Current workflow:
- Type the name of a task in
Add a task to "..." - Click "Set due date"
- Click the date to open the calendar
- Click the desired date
- Click the check mark
Desired workflow:
- Type the name of the task followed by "due:tomorrow"
My suggestion is to have a few "special" keywords like due, priority, or tags. If these keywords appear in the input followed by a colon, the word (or words) following the colon would be assigned to that option's value and both the keyword and value would be removed from the task title. I say "words" because for the due date, it may be required to consider multiple words like "next Thursday" or "March 31, 2022". In this case, we would need a well-defined format for the value.
Here are some values that I think should be supported:
due:tomorrow(set the due date to tomorrow at some default time)due:tomorrow 5pm(set the due date to tomorrow at 5pm)due:friday(would set the due date to 2022/04/01 considering it is now 2022/03/31)due:next friday(would set the due date to 2022/04/08 considering it is now 2022/03/31)due:2 weeks(would set the due date to 2022/04/14 considering it is now 2022/03/31)
I can work on a PR if there is interest (I am a contributor to Nextcloud Cookbook so I know a little about Nextcloud apps)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the add-task workflow and the existing Set due date flow described in the issue. Before implementation, clarify which keywords and date formats are in scope, how values are separated from the title, and how successful parsing should be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100