Allow a team to own a task-list
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 39/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- javascript
- 领域
- backend, full-stack
调研方向
Start by reading the linked team ownership effort in nextcloud/circles and the referenced Deck implementation in pull request 8266; the issue does not name Tasks files or tests. Trace how Tasks represents and displays lists, then compare how Deck handles team ownership. Done means team-owned lists are visible to team members, with task completion attribution and timing; the separate “Team tasks” section is optional.
由索引模型根据 Issue 内容生成。
描述
In the effort of enabling teams to own resources:
In Nextcloud, "Shared with the team" almost always means "owned by a person, lent to the team." With the exception of Team-folders, Collectives, and Talk, resources are bound to a single user; a team is only granted access on top. That makes the team a guest in its own workspace, with important consequences:
- Off-boarding silently destroys team assets. A team is meant to outlive any member, but delete the account of the person who created a resource and it can vanish.
- Team roles don't govern resources. A team owner has no authority over a deck board owned by a member, and removing someone from the team doesn't touch what they own.
Requests
- Please enable a list of tasks to be owned / created by a team
- The list should be visible to all team members
- Maybe the team-owned lists should be sorted under a separate section "Team tasks"
- When someone ticks off a task as done, it would be great if others could see who did and when
Reference
It might help to look at the implementations in the deck and collectives apps:
- 主要语言
- JavaScript
- 星标
- 710
- 派生
- 125
- 平均合并
- 19 小时 37 分钟
- 30 天内合并 PR
- 12
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nextcloud/tasks 的其他 Issue
-
enhancement
难度 1/5 1 小时以内 新手友好度 84/100
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 70/100
nextcloud/tasks#3240 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
nextcloud/tasks#3111 · 1 条评论 ·
维护者通常 1 天内回复
-
feature
难度 2/5 1-3 小时 新手友好度 65/100
nextcloud/tasks#122 · 9 条评论 · 25 个 reaction ·
维护者通常 1 天内回复
-
Calendar for selecting "end repeat" for Recurring Tasks is broken可能已有人在做 @byquanton 于 29 天前认领。 未关闭bug
难度 3/5 1-2 天 新手友好度 65/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
-
难度 2/5 1-3 小时 新手友好度 66/100
remotion-dev/remotion#13341 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
svix/svix-webhooks#2808 ·
维护者通常 1 天内回复
-
enhancement should-have ux
难度 2/5 1-3 小时 新手友好度 72/100