Labels

[unbekanntunity]

Elevator pitch: Labels

The user should be able to create and add labels to tasks like in GitHub or Trello.

Describe how this new feature adds value to the application

The user receives more possibilities to customize tasks and an option to group them. Later this is also useful for filtering or ordering tasks by specific labels.

Describe suggested implementation

N/A

Additional context

N/A

[pobiega]

Terms/Nomenclature

• Is "labels" the term we want to go with? Or would "tags", "pins", "categories" or something else be more appropriate?
• What do other similar programs use?

Feature details

• Do we allow multiple labels per task, or can a single task only have one label?
• Do labels themself have a definition, like in GitHub, or are they just strings we attach to tasks, meaning I could accidentally have both feature and a features labels by mistake, even thou I intended for them to be the same?
• Are there any restrictions to what a label can be? Single word only, or should we support spaces?
• What do other similar programs use?

Suggested implementation

• What would the command syntax for adding/removing labels to tasks be?
• If we define them ahead of usage, what would the syntax be for that?

[unbekanntunity]

Do we allow multiple labels per task, or can a single task only have one label?

• I would say yes

Do labels themself have a definition, like in GitHub, or are they just strings we attach to tasks, meaning I could accidentally have both feature and a features labels by mistake, even thou I intended for them to be the same?

• I would say that we have a list of labels with own ids and owns title and maybe a description

What would the command syntax for adding/removing labels to tasks be?

Create and delete labels

• label add [name] [description]
• label delete [name]/[id?]

Add task with a label

• add [id] [description] [label]
• edit [id] [description] [label] see edit issue

[pobiega]

Add task with a label

• add [description] [label]
• edit [id] [description] [label]

That won't work very well. Imagine the following command: add Test the label system.
How would that parse? There is no difference between a label and a description.

Here is my suggestion: add [+<label> ...] <description> . <> means its mandatory, [] means optional.

Example: add +label1 +label2 This is my description

The point being that anything optional must come before the description, otherwise the parser logic will get very confusing.