nextcloud / nextcloud/circles

Admin page default quota overrides individual set quota's

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

Nobody has claimed this yet.

0. Needs triage bug
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 affected by the same issue.
  • 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.

Steps to reproduce
  1. Log in as an NC admin or user with delegated access to the teams admin settings page
  2. Open the teams admin settings page
  3. Change the default quota and save
  4. Check the quota in the team folder admin settings
Expected behaviour

When the new default quota is lower as what was set individually on the team the admin should receive a warning and perhaps an option to exclude teams from applying the default.

Actual behaviour

The lower default quota applies to the team folder. If you had a 5GB Team folder with 3GB of data and are applied a default 1GB quota you have an issue. As it is now you can never set a lower default quota as the highest individual team quota without causing troubles or analyzing the used storage beforehand.

Server configuration

Latest docker AIO container for Nextcloud 35.

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 reproducing the steps on the teams admin settings page and changing the default quota. Then trace the quota handling for team folders to find where the default overrides an individual quota. Done means a lower default no longer silently creates an invalid situation: the admin is warned and can exclude affected teams or preserve their individual quotas.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.