Disable task list for certain issue templates

[muuvmuuv]

Got that new task list feature and really liking it, but in issues like feature requests or bug issues they are often used to determine which part is involved. For example, in Angular: angular/angular-cli#21202

Would be great to be able to disable this for some issue templates.

[denelon]

Another example of how we use the checkbox not as a task list. Maybe we could get a "radio button" UI/UX for non tasks. #4318

[dgw]

Checkboxes aren't even always tasks. We have a PR template that asks people to agree to the project license, confirm they've linted the code, etc. and all our PRs have "4 of 4 tasks completed" because of it.

Despite it not working for my org's use case, I do like the idea of a "radio button"—easy to come up with alternative syntax based on how the task list/checkbox feature already works: - ( ) Radio button item

[electronicboy]

I concur, I'd also like to add onto this as we use checkboxes as a "please confirm that you've done the following", it would be nice to be able to keep these checkboxes to make people to essentially "promise" us that they're meeting some requirements, e.g. they're actually using a supported version, but, the fact that they show up as tasks is a bit of a "bleh" aspect and makes them unviable to us, which would have been nice!

[pirate]

Sometimes I put mini multiple-choice surveys in issue comments and have people check the boxes to indicate their responses. With this kind of format the 3 of 7 Tasks indicator doesn't make sense, it would be great to disable it for whole issue templates, or for arbitrary specific issues.

[muuvmuuv]

Maybe we just need a option select toggle or something like that. I guess this is what the want us to do in futures using the new issue form builder instead of Markdown.

[DiegoCardoso]

We use checkboxes so the user can check which browsers are affected by the bug they are describing:

[apiraino]

Another similar example of a checkbox list that is not a task list: in the Rust project we use checkboxes to allow selecting which release channels are affected by an issue (our template), example:

[jcsp]

We hit this when trying to use checkboxes to identify which branches to backport issues to (example)

Perhaps it would be sufficient to pick a different bracket character to mean "checkbox but it's not a todo list"

[thejeff77]

I'd really want a way to put multiple on a line -- eg:

DONE / N/A

• / [ ]

So they'd have to tick "N/A" for stuff that isn't applicable.

Or some fast way to cross out the whole line - the markup for that requires manual editing and its painful.

[muuvmuuv]

There is now an option to user a select box with options for that case I mentioned, just fyi. :)

[a-Leong]

Hello, can you explain what you mean by this? I have a use case much like the one you commented on above.

[muuvmuuv]

Here you can see it https://github.com/angular/angular/issues/new?assignees=&labels=&template=1-bug-report.yaml

[syed-a-ali]

Late to the party here but could I please see how the dropdown selection was implemented? I'm attempting to do the same for a pull request template. Attempt at Googling and viewing source code on the page did not bear fruit. Thanks in advance.

[muuvmuuv]

If the Angular example didn't work for you it might be that this feature is just for larger repo>/owners.
https://raw.githubusercontent.com/angular/angular/main/.github/ISSUE_TEMPLATE/1-bug-report.yaml

[syed-a-ali]

Thank you, I understand now, it seems the yaml template is only available for issue report which support these features. Pull request template only has markdown available presently.

[rewati-arista]

There is another hack which stops github from treating it as task list, which is just making these checkboxes as bullet points so doing:

• • Option 1
• • Option 2
    this wont flag them as tasks and you can still select one option :)

[felipelima-circle]

The markdown for this would be something like:

- - [ ] Option 1
- - [ ] Option 2