nextcloud / nextcloud/collectives
add support for user_migration
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 195
- Forks
- 51
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 48
Description
Is your feature request related to a problem? Please describe.
When exporting your user settings for migration, currently the Collectives are not included. We should see if that is possible.
The files are already exported (or, can be), and they would be in the Collective folder, but I suppose without the Teams setup it won't work. I also don't know what happens to any metadata and settings?
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
No files or tests are named. Start by tracing how user_migration exports settings and how Collectives data is stored in the Collective folder, then check the Teams dependency and existing metadata or settings handling. Done means a migration preserves the supported Collective content, metadata, and settings, or clearly documents what cannot be migrated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100