Allow a team to own a task-list

Aperta
  • Qualcosa non va?
#3,318 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
39/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
backend, full-stack

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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:

Lingua principale
JavaScript
Stelle
710
Fork
125
Merge medio
19h 37m
PR unite (30g)
12

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nextcloud/tasks

Tutte le issue di nextcloud/tasks

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.