Feature #20698

Task list Textile/Mardown

Added by Leandro Gehlen about 3 years ago. Updated 9 months ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution:

Description

I think it's necessary to create the task list markdown.

This feature exists in github:
https://help.github.com/articles/writing-on-github/#task-lists


Related issues

Related to Redmine - Feature #20691: Add ballot boxes (☐,☑,☒) to Lists in Wiki Textile/Mardown... New
Duplicated by Redmine - Feature #7601: Checkbox in wiki syntax Closed 2011-02-10

History

#1 Updated by Toshi MARUYAMA about 3 years ago

What is benefit compared to Redmine sub issues?

#2 Updated by Leandro Gehlen about 3 years ago

I think that is the way, that is more easy, and it's possible to check, quickly, which sub tasks are completed

#3 Updated by budo kaiman about 3 years ago

Toshi MARUYAMA wrote:

What is benefit compared to Redmine sub issues?

The syntax can be applied anywhere wiki format is used instead of just for keeping track of tasks. One example is to keep a list of non-task requirements for each version (eg. all code has been reviewed, changelog is up-to-date, etc) in a wiki and check them off as they are validated.

#4 Updated by Toshi MARUYAMA about 3 years ago

Leandro Gehlen wrote:

I think that is the way, that is more easy, and it's possible to check, quickly, which sub tasks are completed

AFAIK, GitHub does not have diff of description, but Redmine has.
"diff" "diff" "diff" ... in issue note is very annonying.

#5 Updated by Toshi MARUYAMA about 3 years ago

budo kaiman wrote:

Toshi MARUYAMA wrote:

What is benefit compared to Redmine sub issues?

The syntax can be applied anywhere wiki format is used instead of just for keeping track of tasks.

Why not use issue with tracker (for example: "house keeping" / "misc jobs").

#6 Updated by Leandro Gehlen about 3 years ago

I think the task-list can be used like steps to follow into a small issue
I think that sub tasks should be used when i have a big issue

#7 Updated by Jens Krämer about 3 years ago

very related to #20691

I also think that would be nice to have (especially if we managed to make these boxes clickable without having to hit 'edit'). For the meantime, you might want to check out the checklists plugin .

#8 Updated by Toshi MARUYAMA about 3 years ago

  • Related to Feature #20691: Add ballot boxes (☐,☑,☒) to Lists in Wiki Textile/Mardown (Redcarpet) added

#9 Updated by Toshi MARUYAMA about 3 years ago

  • Subject changed from Task list markdown to Task list Textile/Mardown

#10 Updated by Toshi MARUYAMA about 3 years ago

#11 Updated by Łukasz Jąder about 1 year ago

Currently we track our issues in GitLab but we want to switch to Redmine.

Our company consists of both technical and business people and the business people get used to Markdown task list ([] and [X]) - it WAY simpler and quicker to use than when creating subissues.

IMHO the world is moving towards Markdown (with GitHub flavor), so should Redmine.

Just my two cents (describing what we, the users, need)...

#12 Updated by Javier Barroso 9 months ago

For some very small tasks that are delegated and that you only have to verify, it would be very useful to have checklists and not subtasks. I prefer read the checklist at the issue description and not to have to use a plugin for it.

Maybe we can use the vimoutliner syntax [ ] and [X]

Thanks !

Also available in: Atom PDF