1 person found this helpful
The first part of your request definitely makes sense.
As User ABC, you should be able to get a list of groups where that use is an "Owner".
This should return all groups that the current user (credentials passed into the API call) is an Owner.
Take this list and iterate over it...
For each record, you could then spawn a request to createMember for that group and specify the new user as an owner.
Note: You could also batch these up into a single (or larger requests) using the Batch Service:
Once the new user is an owner, you can then re-iterate over your previous batch and swap out the user ID and change from "Create" to "Destroy". This will affectively "leave the group" from the user that is currently logged in.
Since there is now an owner in each group, this shouldn't be a problem.
Note: Projects are definitely fickle. They were introduced in Jive before our v3 API took hold, so it is likely that object (which isn't used all that often) may not have full coverage in the API beyond the general "place" stereotype. In general, in the UI...projects can only have 1 owner which is unlike any other container in Jive. In the UI though, you can change the owner through the project settings ... and as an owner of the group ... you have admin rights over the project (so you dont have to be listed as the owner) per say to administer it (if memory serves me correctly).
Hope this helps.