I'm here to get an understanding how many of you have actually come up with the issue and also to find ways how to overcome this.
I'm working in an enterprise size organisation where lots of developers are out sourced from different partners. They're all using our Atlassian environments though.
Code review is a mandatory part of our daily development process and each developer has to submit their changes to the code owner for reviewing.
In many cases the developer and code reviewer are working in different facilities, they haven't met each other face to face and they're employees of different companies.
When a developer has finished his part and has submitted his work for reviewing, he's continuing with new stories.
Quite frequently we've faced a problem that development is not delivered on time and is reaching the deadline. When the deadline has arrived, people get anxious and start approaching the developer. His response is that the code is in review but reviewing is not started yet.
After time consuming investigation it turns out that the code reviewer is on a vacation or out of office.
Is there a way to avoid the situation where code review is not submitted to someone who's not at work?
Hi everyone, We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events