Allow a team to own a task-list

Open
  • Is something wrong?
#3,318 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

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.

Written by the indexing model from the issue text.

Description

1. to develop

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:

Dominant language
JavaScript
Stars
710
Forks
125
Avg merge
19h 37m
Merged PRs (30d)
12

Getting set up

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.

More from nextcloud/tasks

All issues in nextcloud/tasks

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.