nextcloud / nextcloud/deck

Add custom colors for stacks/columns

Open
#8,214 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

Hi.

Currently, it is possible to visually highlight individual cards using colors. However, stacks (columns/lists) cannot be assigned a custom color.

It would be helpful to allow users to choose a color for each stack, for example by adding a colored header, border, or background. This would significantly elevate the readability, make (especially) larger boards easier to navigate and allow different workflow stages or categories to be distinguished more quickly.

Is support for custom stack colors already planned or being considered?

Possible use cases:

  • Visually distinguishing workflow stages
  • Highlighting important or blocked sections
  • Grouping stacks by topic, team, or priority
  • Improving readability on boards with many stacks

Thank you!

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named in the issue. Start by locating the existing card-color implementation and the stack/column rendering and editing entry points, then determine how a stack color would be selected and stored. Done should mean users can assign a custom color to each stack and see it consistently on the board.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.