search

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.81k stars 839 forks source link

Transferring ownership of monitors when someone leaves the team #5141

Open abhole opened 6 years ago

abhole commented 6 years ago

Postman Cloud Bug: We recently had a change in the team and removed someone from our org's postman account. The monitors this person had created were lost as soon as he was removed and we discovered that the next day when we didn't get alerts of the monitor runs. The environments created by this person were also gone from our workspace. The collections created by him were transferred over to a team member so we were able to recreate the monitors

Looks like Collections get transferred over but Environments and Monitors don't which is a bummer since we rely on Monitors running against these environments for our API monitoring.

sanddigital commented 6 years ago

Looks related to #3274

Out of interest, how did you transfer the collections to another team member? Was this completed using the 'Export Collection' and then import?

abhole commented 6 years ago

Well, its kinda related but the one you are referring to pertains to transferring collections. That worked fine for us. we were able to transfer collections.

It's the monitors that didn't get transferred. If this isn't a bug please treat it as a feature request.

-- Akshay

On Thu, Sep 6, 2018 at 1:27 AM Steven Anderson notifications@github.com wrote:

Looks related to #3274 https://github.com/postmanlabs/postman-app-support/issues/3274

Out of interest, how did you transfer the collections to another team member? Was this completed using the 'Export Collection' and then import?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/postmanlabs/postman-app-support/issues/5141#issuecomment-418968928, or mute the thread https://github.com/notifications/unsubscribe-auth/AA8f00sAIRRZ7kT1LA12eKybqrJul-Xmks5uYLI-gaJpZM4Wbwfl .

sanddigital commented 6 years ago

Ok, so how did you transfer the collection owned by the team member that left?

On Fri, Sep 7, 2018, 07:25 Akshay Bhole notifications@github.com wrote:

Well, its kinda related but the one you are referring to pertains to transferring collections. That worked fine for us. we were able to transfer collections.

It's the monitors that didn't get transferred. If this isn't a bug please treat it as a feature request.

-- Akshay

On Thu, Sep 6, 2018 at 1:27 AM Steven Anderson notifications@github.com wrote:

Looks related to #3274 https://github.com/postmanlabs/postman-app-support/issues/3274

Out of interest, how did you transfer the collections to another team member? Was this completed using the 'Export Collection' and then import?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/postmanlabs/postman-app-support/issues/5141#issuecomment-418968928 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AA8f00sAIRRZ7kT1LA12eKybqrJul-Xmks5uYLI-gaJpZM4Wbwfl

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/postmanlabs/postman-app-support/issues/5141#issuecomment-419246345, or mute the thread https://github.com/notifications/unsubscribe-auth/AByU0RtbC6Yx-0-tpq_b2ak2xk6LYnmeks5uYZLJgaJpZM4Wbwfl .

abhole commented 6 years ago

when we tried removing him from our team space the interface to transfer ownership appeared in a pop-up. don't want to risk trying to remove another person right now if I know its not safe anymore!

-- Akshay

On Thu, Sep 6, 2018 at 6:08 PM Steven Anderson notifications@github.com wrote:

Ok, so how did you transfer the collection owned by the team member that left?

On Fri, Sep 7, 2018, 07:25 Akshay Bhole notifications@github.com wrote:

Well, its kinda related but the one you are referring to pertains to transferring collections. That worked fine for us. we were able to transfer collections.

It's the monitors that didn't get transferred. If this isn't a bug please treat it as a feature request.

-- Akshay

On Thu, Sep 6, 2018 at 1:27 AM Steven Anderson <notifications@github.com

wrote:

Looks related to #3274 https://github.com/postmanlabs/postman-app-support/issues/3274

Out of interest, how did you transfer the collections to another team member? Was this completed using the 'Export Collection' and then import?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <

https://github.com/postmanlabs/postman-app-support/issues/5141#issuecomment-418968928

, or mute the thread <

https://github.com/notifications/unsubscribe-auth/AA8f00sAIRRZ7kT1LA12eKybqrJul-Xmks5uYLI-gaJpZM4Wbwfl

.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/postmanlabs/postman-app-support/issues/5141#issuecomment-419246345 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AByU0RtbC6Yx-0-tpq_b2ak2xk6LYnmeks5uYZLJgaJpZM4Wbwfl

.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/postmanlabs/postman-app-support/issues/5141#issuecomment-419257165, or mute the thread https://github.com/notifications/unsubscribe-auth/AA8f03nmk7sQy58TegGS18J9LpLeJxzcks5uYZz2gaJpZM4Wbwfl .

jomel commented 4 years ago

really @ankit-m not a bug?!!

We just became "victim" of this too.

Our process was:

  1. make sure that any collections that the person owned were "shared" or "forked" to the team workspace.
  2. make sure that all relevant environments are "team workspace" environments
  3. ( since the monitors rely on accessing a specific collection and environment (in this case both on a team workspace) we expected those to be attached to the "workspace" )
  4. remove person from team.
  5. this person no longer has access to the team collections.

[here comes the bug]

  1. this person still "owns" the monitors that are attached to the team collections, and gets a notification when those are run.
  2. When we logged in as that person we could not find the monitors (as they were on the team workspace, and this person no longer has access, so it's not in the dropdown)
  3. we then re-added the person to the team, and now we could see the monitors in his online dashboard, but all monitors had no "collection" or "environment" set in the dropdowns!! There is no button or option to transfer ownership.
  4. we had to manually re-create all monitors on another persons account, and delete those owned by the person leaving.
  5. curse postman
seanlandis commented 3 years ago

We were bit by this too. It seems the best approach would be to allow someone with Admin role, to reassign owners.