Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Needs Info status

jason voegeli
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!
December 12, 2023

We often have a scenario during the PR code review process where someone does the review, but only has questions for the submitter. No changes are being requested. Only questions and they are finished with their review. They then mark the PR as Needs Work while waiting on answers to their questions, so that the PR drops to the bottom section of the PR summary list. If the submitter then responds to those questions without any new commits, the PR stays in Needs Work state and remains at the bottom of the PR summary list, and the reviewer isn't able to easily see that it's back in their court. Our project is large and we have a lot of users, so it's nearly impossible to monitor this effectively through email notifications. Is there any way to mark a PR as "needs info", where the submitter could then mark it as "info provided" after they have answered the questions, and then the reviewers would know it's ready for them again?

1 answer

0 votes
Saxea _Flowie_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 12, 2023

Hi @jason voegeli

You could implement this workflow using Flowie labels set(a Bitbucket addon we provide). You could, for instance, create a label "Status: Ready to review" and "Status: Info required" to reflect the status of the PRs.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events