Admin page storage quota shows wrong value
Nobody has claimed this yet.
- 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
- Log in as an NC admin or user with delegated access to the teams admin settings page
- Open the teams admin settings page
- Change the quota on the team (notification that the quota changed)
- Click another page or reload the page.
Expected behaviour
The quota field should show the quota you set.
The nextcloud logging admin settings page should show the result of the action.
Actual behaviour
The quota value shows the default setting. (Changing the default quota works like expected and shows correctly on the storage quota field)
The team folders app shows the correct value for the quota.
Server configuration
Latest AIO docker release for Nextcloud 35.
Browser
Browser name: Edge
Browser version: 153
Operating system: Windows
Browser log
No console log.
Network log gives 200 ok
{
"ocs": {
"meta": {
"status": "ok",
"statuscode": 200,
"message": "OK"
},
"data": {
"success": true,
"folderId": 52,
"folder": {
"id": 52,
"quota": null,
"mountPoint": "NumberOne"
}
}
}
}
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
Start by reproducing the problem in the teams admin settings page and inspect the quota update and reload responses. Compare the displayed value with the team folders app's value and check the nextcloud logging admin settings page. Done means a team-specific quota remains visible after navigation or reload and the action is logged correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100