What Happened to Sharing a collection/environment across Workspaces

The option to “Share” a Collection or Environment Definition used to be present so that the object could be accessed from different collections. (I Noticed this change in version 9.1.1)

With the latest version of Postman All I see when I Select the “Share” option is “Share link to the collection/environment” or “Move collection/environment

What is a person supposed to do with the “URL” to an collection/environment, when what I want is to access an environment definition in another workspace.

I don’t want to MOVE the Environment Definition!!!

I need the “environment definition” in question to be accessible in multiple workspaces without having to have and maintain multiple copies of the same object. for the last 4 years we have built our entire Postman Usage Model around this.

We have more than 30 Collections spread across multiple workspaces that use common environment definitions which can be Edited in any of the respective workspaces and the changes are reflected for all workspaces.

This latest change is NOT an enhancement, it is in fact a detriment!!!

5 Likes

Same. Oddly it’s accessible via webUI

1 Like

I noticed that after I had posted…
So this is a “Work around”
Hopefully they won’t deprecate this from the webUI

I have the same issue. And It’s not accessible in the webUI anymore either.

Hey POSTMAN!!!

Taking this Feature away REALLY SUCKS!!!

You have just “BROKEN” a very large portion of our usage Model.

Why have you taken this away!!!

This is MOST DEFINITLY NOT a good thing.

Please Bring it back!!!

Also frustrated by this! The web UI has been updated so can no longer be used as a workaround for me.

The feature has indeed been removed, as of the current version (I’m using 9.5), on the web and in the application.

Instead, you are supposed to either have your team all use the same Workspace, or “fork” the Collection or Environment to their personal Workspaces. There will soon be a way to do a Pull Request and have team members push their changes back to the original. But I don’t know how all the other team members would then pull the pushed changes back into their personal Workspaces, without forking again! There must be some new workflow they are cooking up that hasn’t been released yet. Until then, we are stuck with the partially-implemented and more complex fork functionality!!

I’ve contacted support and registered my frustration with the removal of a simple “share” function. they are reporting it to their product team. I included a link to this discussion.

1 Like

Yeah, I got a similar response…

We have ~7000 requests across 33 collections that depend on a single environment definition
We have the collections spread across 3 workspaces for ease of manageability.

We are now having to manually update the Environment Definitions in all 3 workspaces because they are no longer “sync’d”.

Previously a change made in one workspace Environment Definition was instantly propagated to the other workspaces.

Creating “forks” doesn’t replace that functionality… someone still has to do “Pulls/Pushes/Merges”…

POSTMAN:
This is a Significant Reduction in the usability and Desirability of this product!!!

I agree with all the previous comments. This is definitely a loss of functionality from our perspective.

One interesting observation is that if a collection was previously shared with multiple workspaces you can still add new requests, and folders, and they will be synced. The core functionality is still present in the current version.

If some new sharing model is being developed, please roll it out soon. We were just about start a large team initiative to add many API tests. This loss of functionality is a significant impact for us.