✨ Feature Request
Is your feature request related to a problem? Please describe.
Currently, the card description does not fully support interactive checklist formatting such as Markdown checkboxes (- [ ] / - [x]) or advanced README-style formatting. This makes it harder to organize tasks, track progress, and create structured checkpoints inside a card.
Describe the solution you'd like
Add support for:
- Markdown checkboxes
- Nested task lists
- README-style Markdown rendering
- Progress/checkpoint tracking inside cards
Example:
# 🚀 Mission Progress
- [x] Setup project
- [x] Create structure
- [ ] Implement features
- [ ] Testing
This would help users create cleaner workflows and better task organization directly inside cards.
Describe alternatives you've considered
Currently, users need to:
- Use plain text lists
- Create separate checklist items manually
- Use external tools for Markdown rendering
These alternatives are less efficient and harder to maintain.
Additional context
Supporting full or partial README-style Markdown would improve usability for developers and productivity-focused users who rely on structured documentation and task tracking.
Implementation ideas (optional)
Possible implementation ideas:
- Add Markdown checkbox parsing
- Support GitHub-flavored Markdown
- Auto-convert Markdown task lists into interactive checklists
- Render nested checklists properly
Would you like to work on this feature?
✨ Feature Request
Is your feature request related to a problem? Please describe.
Currently, the card description does not fully support interactive checklist formatting such as Markdown checkboxes (
- [ ]/- [x]) or advanced README-style formatting. This makes it harder to organize tasks, track progress, and create structured checkpoints inside a card.Describe the solution you'd like
Add support for:
Example:
This would help users create cleaner workflows and better task organization directly inside cards.
Describe alternatives you've considered
Currently, users need to:
These alternatives are less efficient and harder to maintain.
Additional context
Supporting full or partial README-style Markdown would improve usability for developers and productivity-focused users who rely on structured documentation and task tracking.
Implementation ideas (optional)
Possible implementation ideas:
Would you like to work on this feature?