Workzone reviewer priority

[Brent Hessell]

Hello
I have recently started using workzone (v7.9.4) and have unexpected results in the reviewers section.

I work on a large application, with multiple teams working in different parts of the system.  The different teams name their branches so we can identify which team it is.  We then have reviewers based on source branch, I.e.
Source branch is Team1 -> reviewer group for team 1
Source branch is Team2 -> reviewer group for team 2 etc, with a catch all at the end
Any branch -> default reviewer list.

What I am seeing is a branch for Team 1, team 1 reviewers plus default reviewers are being added. It appears both rules are being matched and applied, not just the first in the list as I was expecting.

Has anyone else noticed this behaviour?

Thanks

[Brent Hessell · Accepted solution]

From the support call that was raised.  This is a bug in v7.9.4 of workzone, and has been fixed in v7.9.10

[Ulrich Kuhnhardt _IzymesCo_]

Hi @Brent Hessell 

Thanks for sharing your observation. I'm happy to support you with this issue. 

I think you have set up Workzone correctly. Please be aware that Bitbucket repository default reviewers which are defined outside Workzone are added by Bitbucket.

Best way forward is to create a support request with us so we can handle your data confidentially and reproduce your specific issue.

Best, Ulrich

// Izymes - Workzone