nextcloud / nextcloud/circles

Teams admin page team list V2

Open
#2,804 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 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

Let's discuss how to expand the list of teams and their folders - https://github.com/nextcloud/circles/issues/2781

We should provide some more transparency there, with a few possible changes:

  • add search and sorting on top
  • Add more information. In particular:
    • visibility setting
    • sharing settings: federated sharing allowed, the not-yet-existing "allow sharing of team owned resources", password protection, ...
    • invitation settings (esp if moderated or free-join)
    • members - have a button to see all members.
    • resources - have a button to see all resources owned by the team
    • are resources of the team shared outside the team (yes, no, if yes - show which)
    • are resources of the team shared outside the organization (public links) (yes, no, if yes - show which)
    • group the team is in (once we assign those)
    • who initially created the team?

Not saying we should do all ;-)

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

Start by reviewing the Teams admin page and the linked discussion in issue #2781. Clarify which list improvements are in scope, including search, sorting, team settings, members, and resources; done would require an agreed subset and corresponding transparency in the team list.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.