Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Allow configuring a board to restrict task cards to a single assignee

未关闭
  • 哪里不对？
#8,400 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
68/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript
领域
frontend

调研方向

首先在 frontend 中找到 board 设置 UI 和卡片负责人编辑器。跟踪 board 偏好设置和负责人变更的存储方式，然后实现默认的多负责人行为以及可选的单负责人强制规则。完成的标准是：启用该设置后，编辑过的卡片仅限一名负责人，未编辑卡片的现有分配保持不变，并且仍允许没有负责人。

由索引模型根据 Issue 内容生成。

描述

feature: cards needs discussion
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.
Background and problem

In many project management tools, it is possible to configure whether a task can be assigned to multiple people or only to a single person.

In Nextcloud Deck, a card can currently be assigned to multiple users. While this can be useful in some situations, it can also make it unclear who is ultimately responsible for ensuring that the task is completed.

For my workflow, the person assigned to a card represents the person responsible for that task. This does not mean that they have to complete the task alone; they can still collaborate with other team members. However, there should be one clearly identifiable person responsible for the task.

When a piece of work needs to be handled independently by several people, I would create separate cards and assign each card to one person. This makes ownership explicit and makes it easier to see who is responsible for each task.

Preferred solution

Add an optional board-level setting that allows users to choose between:

  • Multiple assignees: the current behavior, where a card can be assigned to multiple users.
  • Single assignee: a card can have at most one assigned user.

When Single assignee is enabled, assigning a new user should replace the current assignee. If the card already has multiple assignees, assigning a new user should replace all existing assignees, leaving only the newly selected user assigned to the card.

A card should still be allowed to have no assignee. The restriction is about having at most one assignee, not requiring exactly one.

If the setting is enabled on a board where some cards already have multiple assignees, existing assignments should not be changed automatically. The single-assignee rule should instead take effect when the assignee field is next edited. When saving the changes, the UI should enforce that the card has no more than one assignee.

A frontend-only implementation would be sufficient for an initial implementation. The goal is to help teams enforce a workflow convention, rather than to provide a strong security mechanism. If a team deliberately bypasses the convention through the API or other means, this should not necessarily be considered a problem.

The default should remain Multiple assignees, so existing boards and workflows are not affected.

Considered alternatives

A separate "responsible person" field could be introduced while keeping multiple assignees. However, this would add another concept to Deck and could make task ownership more complicated.

主要语言
JavaScript
星标
1.4k
派生
358
平均合并
2 天 3 小时
30 天内合并 PR
89

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

nextcloud/deck 的其他 Issue

查看 nextcloud/deck 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。