nextcloud / nextcloud/groupquota
Unclear information
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 35
- Forks
- 10
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
I created a group "Test 1" and set the group quota to 10GB. Then I created a user with the registration app. The standard user quota is 2GB on my test environment.
After the registration the user is logged in automatically. I at first see a remaining diskspace of 2GB, then I delete the example files and see 10GB. After deleting the example files from the trashbin and returning to the home folder of the new user I see remaining disk space of 2GB.
The admin user information shows that user with 10GB alotted space.
Steps to recreate:
Set standard user quota to 2GB
Set group quota of Test-Group to 10GB
Register new user, with standard group from Registration app being Test-Group.
Expected behaviour:
See remaining space of 10GB in files as user.
See alotted space of 10GB in user manager as administrator.
Actual behaviour:
See remaining space of 2GB in files as user
See alotted space of 10GB in user manager as administrator.
Also quick question: Is this app to set a standard per user quota per group they are being put in? Or is this setting a quota for all users in the group. So if one uploads 8GB of data, the rest can't upload more than 2GB? The description of the app is a bit lackluster there.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the flow using the Registration app with a 2GB standard quota and a 10GB Test-Group quota. Compare the quota shown in Files for the new user with the value in the admin user manager, then verify whether the group quota applies per user or across the group. Done means the effective quota is consistent and the group-quota behavior is clearly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100