nextcloud / nextcloud/deck

Feature request: Implement card voting mechanism

Open
#7,591 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

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.

In boards used for collecting ideas, feature requests, or backlog items, it is currently difficult to understand which cards are most important to users. All cards have the same visual weight, and prioritization requires manual discussion or external tools. This becomes frustrating when many users want to express preferences / prioritization or support for specific ideas.

Describe the solution you'd like

Add a voting system to Deck cards that allows users to vote (e.g. upvote) on cards.
Each card should display its vote count, and the deck should support sorting or filtering cards by number of votes (for example: highest votes first, lowest first, etc.).

This would enable team-driven prioritization of ideas, similar to >> see Additional context

Describe alternatives you've considered

Using other tools

Additional context

This feature would be especially useful for:

Internal product or roadmap prioritization

Comparable implementations exist in tools like:
Salesforce Ideas,
Trello voting power-ups, (https://trello.com/power-ups/55a5d917446f517774210013)

Please find bellow an exemple of a similar voting system
https://pm.zimbra.com/b/features

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

The issue does not name any files, tests, or entry points. Start by tracing how Deck cards are stored and rendered, then identify the existing card ordering and filtering paths. Done should include user voting, visible vote counts, and sorting or filtering cards by vote count, with behavior covered by the relevant tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.