nextcloud / nextcloud/tasks

Smart add tasks with shortcuts?

Open
#3,060 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
706
Forks
117
Avg merge
8h 50m
Merged PRs (30d)
18

Description

Is your feature request related to a problem? Please describe.

Not a problem, it's only something I've seen in another app that I like very much and would like to ask if it's on the roadmap for "Tasks".

Describe the solution you'd like

Coming from RTM (rememberthemilk), I inserted my first task in the Nextcloud Tasks interface using "smart add" feature (see https://www.rememberthemilk.com/help/answer/basics-smartadd-howdoiuse ), and noticed that it works for tags: if I write my task description and add a word preceded by "#", it's recognized as a tag.
Questions:

  • where is this behaviour described (word with prepended "#" recognized as tags)?
  • are there other such "smart add" features (e.g. "^" for due date, "!" for priority, "@" for location, "*" for recurrence,...) already present in Tasks? Which one, and where are they described?
  • if importing Tasks from ics, the "DESCRIPTION" field does not consider words with prepended "#" as tags, is there a technical reason for this?
Describe alternatives you've considered

(Painfully) insert all the informations with mouse.
I'm willing to give more info if you want to go down this road, and to test features!

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names the Tasks interface, smart add behavior, and ICS DESCRIPTION importing but no files, tests, or entry points. Start by checking how task text and ICS descriptions are parsed, then verify which prefixes are supported and documented; done means the behavior and any implementation or documentation scope are clearly established.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
data, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.