only ordered task lists should count towards task total #4836
Replies: 2 comments 8 replies
Why not use multiple issue templates or labels for this? Those are the appropriate GitHub features to use for this. Forcing the use of ordered lists in Markdown is very opinionated and would force users to use improper semantics (i.e. ordering a list that doesn’t need to be ordered). When I’m making a list of tasks for an issue, I don’t necessarily care what order they are achieved in. When I do care, I’ll use an ordered list. |
|
I like this idea. Using bullets for one purpose and numbered lists for another is a very elegant and simple solution to this contentious issue. The only issue I see with this suggestion is that existing task lists would break, but could be handled with an repo setting that modifies markdown behaviors. |

Uh oh!
There was an error while loading. Please reload this page.
Summary
Distinguish between task list types (ordered vs unordered) in an issue to provide users better management of the task count that gets displayed in the GitHub UI.
Description
Often times an issue (via template or hand made) may contain a list of options to prompt a user through a set of options, like the below to determine what the issue "type" is:
Assuming a user "checks" N number of those items, the issue total will display as N / 5 tasks in the UI

Probably even more common in an issue is to (also) track tasks, goals, TODOs, or other issues (like an Epic).
Whatever you need to do to "close" this issue. So you might add something like this.
Combined with the above issue type list, you'll now see N / 8 tasks in the UI.

Proposal
Given the above example, if an ordered task list is used in a GitHub issue, only those tasks should count towards the task count.
So in this case you would actually see 3 Tasks in the GitHub UI (since none of the tasks in the Requirements section are checked, but there are 3 of them)

Thoughts
Some thoughts / questions:
If both are no, then would love to see this feature! 🙏
All reactions