We migrated Crowd from one server to new Server. After the migration, Workzone plugin auto reviewers for Pull Request stopped working.
Only newly created Reviewers are showing up , but the one created b4 were not showing up.
Arun, not completely sure why the new set of crowd users are not recognised. I suppose they have the same usernames and group memberships? The only reason I can think of is that Bitbucket checks permissions against user's uuids which may differ between old and new crowd instance.
You can retrieve existing Workzone reviewer, auto merge and workflow hook configurations via the workzone REST API and also configure the same again with users from the new crowd instance. Please see the comment in issue #125 from 2015-09-10
Users are not added to new Pull Requests - right. The reviewers are configured earlier which was auto populating whenever we create new Pull requests. But after we moved to new Crowd Server, those reviewers are not auto populating any more. But when I create a new set of reviewers for the Repo, they are working as expected. The configuration which we did earlier is not working or showing up automatically. Is there a way to find all those configurations and deleted and readd them in backend ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry for the trouble. Could you please elaborate what stopped working? Are users not listed in the workzone reviewers configuration? Are they not added to new Pull Requests?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.