nextcloud / nextcloud/polls

Add a two-dimensional grid / an array of time and location/duty

Open
#3,124 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
284
Forks
91
Avg merge
4d 3h
Merged PRs (30d)
50

Description

⚠️ This issue respects the following points: ⚠️
Describe the goal you'd like to achieve

As a poll owner, I want to be able to add a two-dimensional poll, because it helps to assign duties for e.g. a small festival at a school, etc.

Describe possible solutions

So for multiple times there are multiple options or a list of options to choose from.
Ideally you can specify the max number of votes/assignees per duty.

time option 1 option 2 option 3 ... option N
time1 11:00 - 12:30 votes[1/1] votes[2/1] votes[3/1] ... votes[N/1]
time2 12:30 - 14:00 votes[1/2] votes[2/2] votes[3/2] ... votes[N/2]
... ... ... ... ... ...
timeM 15:30 - 16:00 votes[1/M] votes[2/M] votes[3/M] ... votes[N/M]

Top-down should be time of day
left-right should be the order of the duties by default

Caveat: there may be a different list of duties per time of day.

But the two axis could be switched if necessary / wanted for display purpose.
An additional plus would be to filter on a specific duty option / time row/column.

Additional context

I got the idea from a tool in german: www.standeinteilung.de

standeinteilung

Here is an example from the setup & configuration screen

setup

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 files, tests, or entry points are named. Begin by surveying how polls, times, duties, votes, and assignee limits are represented and rendered, then define the data model and interaction design for the two-dimensional grid; done means the feature supports the described axes, per-cell limits, differing duties by time, axis switching, and filtering.

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
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.