Allow users to move projects between teams
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Problem to solve
Currently, users can add or remove projects from a team. The addition and removal process contains some friction that could be avoided when a user simply wants to transfer a project to another team.
Also, while prebuilds are not removed, removing the project will remove access to existing prebuilds and prebuilds logs from the dashboard.
Proposal
Introduce a way to move a project to another team from the project settings.
Additionally, in the future we could consider dropping all prebuilds, removing the prebuilds configuration (webhook, etc) (https://github.com/gitpod-io/gitpod/issues/5517), etc. However, moving a project could justify keeping the prebuilds and configuration. 💭
Designs
TBD (To be discussed)
This could introduce a small section under General project settings with one action button that triggers a modal to select a namespace to transfer the project to. 💭
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 with the project settings area and the proposal to add a transfer action and namespace-selection modal. Designs are still TBD, so clarify the interaction and scope before implementation. Done should include a way to move a project to another team without the friction of separate removal and addition steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100