nextcloud / nextcloud/deck

More descriptive information for each vertical lane

Open
#5,403 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Is your feature request related to a problem? Please describe.

I'm using each column to describe a step in a process, We use deck to track booking gigs for my band.
image

Each step has information/todo lists/reminders that need to be completed before the gig can move to the next step. Right now I'm using a card that we keep at the top of the lane to track this information.

We then use the individual gig card to track all the info and attachments related to the gig.

Describe the solution you'd like

  1. Some way to "Pin" or lock the informational card so it can't get easily deleted or
  2. some way to add more descriptive info to the title of the column
  3. let the title of the column word wrap so we don't lose the text if it's too long

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, test, or implementation entry point is named. Start by reviewing the Deck board's vertical lane interface and the screenshot, then determine which of the three requested approaches is intended. Done should mean lane guidance remains visible without accidental deletion or truncation, with the chosen behavior covered by the relevant UI checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.