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.
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 ?
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
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot