What is best practice to track development and code review time?

Sharayu Jagtap
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 20, 2023


If dev1 worked on one ticket and moved it to ''In Development => 'Code Review'. Then dev2 reviewed changes and requested changes regarding few best practices. 

Practice 1 -
So do dev1 need to move ticket back to 'In Development' and after addressing all comments move back to 'Code Review'


Practice 2-
dev1 work on comments addressed by dev2 but keep ticket in 'Code Review' and once ready as dev2 to re-review it.

1 answer

0 votes
Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 2, 2023

@Sharayu Jagtap Welcome to the Atlassian community

It really depends on your process and what you are tracking in that process.  For instance it might be important to know how many times a developer has something come back to be worked on after code review.  Then having it go back a forth in a status can help you track this and determine which developers needs additional training and support.  These are things that you should determine in your process and then have your workflow match the process.

Brant Schroeder
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 10, 2024

@Sharayu Jagtap can you accept this answer to help others?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events