postmanlabs / postman-app-support

Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster.
https://www.postman.com
5.87k stars 841 forks source link

Migrating/Cloning Workspaces #10494

Open Kcorb95 opened 2 years ago

Kcorb95 commented 2 years ago

Is there an existing request for this feature?

Is your feature request related to a problem?

After setting up a workspace and members creating forks (environment files with their own settings), there does not seem to be a way to migrate or clone the entire workspace including environment files to a different account with a paid license.

It would appear that most things can be transferred if I import as a GitHub repo, but this doesn't take care of forks. If there was an easy way to do this at the workspace level as a whole, it would reduce friction in switching from a free to paid licenses.

Describe the solution you'd like

An easy way to migrate or clone a workspace on a different account without having to fork each collection etc. individually.

Describe alternatives you've considered

No response

Additional context

No response

akshay-kulkarni-03 commented 2 years ago

Hi @chrisdeso thanks for opening this feature request. We are discussing the feasibility, usability of this feature internally. Will update this thread once I have more information on this.

calebruz commented 2 years ago

Yes. Please. I recently attempted to clone via postman API, which worked, but from what I was told is that those collections remain attached to the original workspace. This means that deleting the new workspace also emptied the original workspace. There was no documentation about this outcome that I could find.

This is also an issue with moving collections between workspaces. There should be an option to move or copy. Currently, if you want to move a copy to a different workspace you have to duplicate and move which could be reduced to just adding a checkbox to the move modal asking if the user wants to move a copy vs the collection itself.

MincDev commented 2 years ago

Any feedback on this?

LockTar commented 2 years ago

Cloning a workspace would be very handy! Inside the same account is voor me personally enough. Just ask for the new name or let people just select the target workspace (so you would first need to create an empty one).

davidbrenner-insight commented 2 years ago

My company has recently upgraded our postman licenses. I'd like to move my workspaces from my personal system to the team environment without having to export/import everything piece by piece. One export and one import for the whole workspace would be rather convenient.

JaggedJax commented 2 months ago

I'm excited to waste my day doing this. Let's just say it wasn't my decision and I would have just taken the opportunity to move elsewhere.