mirror of
https://github.com/plankanban/planka.git
synced 2026-02-25 03:14:50 +03:00
[ Cards / Custom Fields ] – Add Dropdown Support to Custom Field Configuration #832
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 12, 2025).
Is this a feature for the backend or frontend?
Backend, Frontend
What would you like?
[ Cards / Custom Fields ] – Add Dropdown Support to Custom Field Configuration
📝 Description
Planka currently supports custom fields on cards, but all inputs are freeform text. This limits consistency and makes filtering or scanning across cards error-prone. Platforms like Trello and Linear support dropdown/select-type fields, which enforce structured input and improve UX. Adding dropdown support — with optional color tagging per option — would bring Planka closer to parity and enhance builder control.
Why is this needed?
💡 Use Case
As a builder, I want to define a custom field with a dropdown list of predefined options so that users can select from a controlled set of values. This ensures consistent labeling across cards (e.g., application names, priority levels, team assignments) and improves filtering, sorting, and visual scanning.
Additionally, the ability to assign a color to each dropdown option allows for faster visual parsing and semantic grouping — especially useful for priority levels, status indicators, or team roles. Freeform text fields currently allow typos and inconsistent formatting, which undermines data integrity and slows down card review.
✅ Expected Behavior
• Custom field configuration supports a new type: dropdown.
• Dropdown fields accept an array of predefined options.
• Each option can include:
◦ A label (string)
◦ An optional color (hex or theme token)
• Field appears as a dropdown in the card UI.
• Selected option is rendered with its assigned color (e.g., pill-style or inline tag).
• Only one option selectable per field (multi-select could be a future enhancement).
• Filtering/searching by dropdown value is supported.
• If no value is selected, fallback behavior applies (e.g., empty state or default option).
• Dropdown styling matches existing card field UI and respects color tokens.
• Configurable via both builder UI and API.
🚀 Why It Matters
• Enforces consistent data entry across cards.
• Improves UX for builders and collaborators.
• Enables better filtering, sorting, and reporting.
• Aligns with UX patterns in other project tools.
• Reduces manual errors and improves layout clarity.
• Color tagging enhances visual scanning and semantic grouping.
• Supports scalable workflows for teams managing multiple applications or categories.