Move owner to next person when current owner is deleted
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
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.
Is your feature request related to a problem? Please describe.
Since a Deck is personal and belongs to the user that created it (if not owner is changed) and that user are removed (quitting the job or whatever reason) then the whole Deck access becomes forbidden for the other users.
It's too much administration to change owner every time a user are removed, and it's too much to ask for to expect a novice user (that just wants things to work) to change owner before they quit and are removed.
Describe the solution you'd like
It would be much better if it worked like in Circles where the next person in the list of "members" are promoted to owner if the owners account are deleted from Nextcloud.
Describe alternatives you've considered
Sure, one could use Circles and add that as the owner for all the Deck cards, but once again, it's too much to ask for in an organization with 500 ppl. If one of them misses out on doing so, and then are removed, a ton of work could be lost.
Additional context
Question came up from one of our Government agencies in Sweden that are about to launch Nextcloud in full scale now in October.
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 locating how Deck ownership and membership are handled when a Nextcloud account is deleted, then compare the requested behavior with Circles' owner promotion. Define the ordering for choosing the next member and verify that remaining users retain access after deletion, including coverage for the relevant removal scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100