nextcloud / nextcloud/circles

Create a projects/sub-teams concept

Open
#2,636 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
177
Forks
68
Avg merge
2d 22h
Merged PRs (30d)
60

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • 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.

Feature request

Make it possible to create sub-teams or projects in a main team which share resources and membership.

Use case

When in a Team that exists for a longer time - think of a real organizational department - it might make a lot of sense to create sub-teams for smaller projects.

Properties

Projects should:

  • be visibly grouped under the team (visible on the team page and in the Teams app)
  • be accessible to all members of the top level team
  • Follow member permissions and roles from the top level team
  • not allow further sub-groups to avoid/limit complexity

Open questions

Lots more thoughts probably needed here:

  • what happens when you invite someone from a different team just to a project? What resources and permissions do they get?
  • Can you have more permissions in a project than in a team, for example, view-only on team but read-write on the project?

Plenty to discuss.

MVP

Marco had an idea for an MVP which would 'just' have the project/sub-team be a team created with all team members and view modified to show it under the main team.

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. Start by reviewing how teams, membership, roles, permissions, and the Teams app are currently represented, then resolve the open questions about invited members and differing permissions before defining the MVP; done means a decided, implementable project/sub-team design.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authorization, backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.