We currently use bitbucket feature branches for development, and protect merges to the main branches with branch permissions. Developers must raise PR's for their changes to be merged, and there is a code review process to help ensure code quality and correctness.
The process is pretty much as described here: https://confluence.atlassian.com/bitbucket/pull-requests-and-code-review-223220593.html
The code review process may result in a number of updates to the code from the developer, and further time to review the updates, as described in the document above.
The question is how do we track how much time is spent "reviewing" the code vs. how much time is spent making code updates to address review comments. We would _like_ to reflect this in the status of the JIRA ticket, however, unless we "decline" the PR, there is no hook to automate the state transitions. The article above describing the recommended (?) process suggests the PR's are left open, and this is how we currently work, and it provides a number of benefits in referring to the discussion and task history in following reviews.
Thanks in advance
Rob
