starred/planka-plankanban
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-05-04 18:00:55 +03:00
Code Issues 398 Packages Projects Releases 10 Wiki Activity

Use the same visual editor for comments as for card description #912

New Issue
Open
opened 2026-02-05 18:54:01 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-05 18:54:01 +03:00
Owner
Copy Link

Originally created by @kbakaras on GitHub (Feb 4, 2026).

Which part of the project does this feature apply to?

Frontend

What would you like?

It would be great if comments used the same visual editor as the card description.
In short: comments already support Markdown rendering, but lack a visual editor during editing. Reusing the existing description editor for comments would significantly improve usability.

Why is this needed?

Currently, Planka provides a convenient visual (WYSIWYG) editor for the main card description, which makes writing and editing formatted content very comfortable.

However, comments use a plain text editor during input. At the same time, Markdown syntax entered in comments is rendered correctly after saving, which indicates that Markdown is already supported at the rendering level.

It would be great if comments used the same visual editor as the card description. This would:

  • Improve consistency of the user experience
  • Make writing structured comments (lists, emphasis, links, etc.) more convenient
  • Reduce the need to manually write and preview Markdown syntax

Other information

Version: Planka 2.0.0-rc.4

Originally created by @kbakaras on GitHub (Feb 4, 2026). ### Which part of the project does this feature apply to? Frontend ### What would you like? It would be great if comments used the same visual editor as the card description. **In short:** comments already support Markdown rendering, but lack a visual editor during editing. Reusing the existing description editor for comments would significantly improve usability. ### Why is this needed? Currently, Planka provides a convenient visual (WYSIWYG) editor for the main card description, which makes writing and editing formatted content very comfortable. However, comments use a plain text editor during input. At the same time, Markdown syntax entered in comments is rendered correctly after saving, which indicates that Markdown is already supported at the rendering level. It would be great if comments used the same visual editor as the card description. This would: * Improve consistency of the user experience * Make writing structured comments (lists, emphasis, links, etc.) more convenient * Reduce the need to manually write and preview Markdown syntax ### Other information Version: Planka 2.0.0-rc.4
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka-plankanban#912
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?