mirror of
https://github.com/plankanban/planka.git
synced 2026-02-05 00:39:58 +03:00
[ Custom Field Groups ] - Allow Custom Field Groups to allow Rich Text #845
Reference in New Issue
Block a user
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?
Originally created by @NDCallahan on GitHub (Oct 23, 2025).
Is this a feature for the backend or frontend?
Frontend
What would you like?
As a project manager using Planka to track complex workflows, I want custom field groups to support rich text formatting (like the description field), So that I can structure detailed notes, embed links, and format content for clarity within grouped custom fields.
Why is this needed?
Custom field groups are powerful for structuring card metadata, but their current plain-text limitation makes them unsuitable for nuanced or richly formatted content. Many teams use Planka to track specs, checklists, or multi-step processes that require:
• Clear formatting (e.g., bold headers, bullet points, code snippets)
• Embedded links to documentation, tickets, or external tools
• Semantic structure for readability and collaboration
Without rich text support, users are forced to cram complex content into unformatted fields or overload the main description. This creates friction, reduces clarity, and limits the utility of grouped fields for real-world workflows — especially in technical, editorial, or compliance-heavy contexts.
Enabling rich text in custom field groups would unlock more expressive, modular, and maintainable card layouts — without sacrificing the clean separation of concerns that groups provide.
Other information
• This expands on #1381 by enabling richer semantic structure within grouped fields, not just layout.
• Ideal for workflows involving technical specs, multi-step instructions, or embedded references.
• Could be implemented as a new field type (richText) within the group config.
• Custom field groups can be configured to use a rich text editor (same as the description field).
• Markdown or WYSIWYG formatting is supported: bold, italics, lists, links, code blocks.
• Rich text fields within groups are editable inline or via modal, consistent with existing UX.
• Field data is stored and rendered safely across board views, card modals, and exports.
• API and database schema support rich text content for grouped fields without breaking existing plain-text fields.
Screenshots