I have two questions.
- The author/moderator creates a review; then reviewer raises some defects, the author fixes those defects but here how does the author mark/highlight that the defect is now fixed. This way that defect stops appearing on the comment search utility.
- Secondly, it seems that the author can close a review even with open defects/comments. How can we prevent the review from getting closed when there are open comments/defects (I want to avoid the scenario when the author cannot fix the defect and he simply closes the review to improve his statistics). Is it possible that the reviewer performs some kind of validation that the defect is now fixed to his satisfaction and only then the author can close the review.
Crucible is very forgiving -- you can close a review with no reviewers, for example, but its reporting tools don't take this into account. In my opinion, better reporting tools are more useful than more strict controls.
There's at least one 3rd party reporting plugin (https://marketplace.atlassian.com/plugins/biz.deref.flyover.flyoverForCrucible) that's much more thorough.
We use a Custom Classification called "Status" to show whether a defect is Open or Resolved, but Crucible doesn't recognize it, so we have to manually verify that all defects are "Closed" before closing the review. Crucible Advanced Search makes this only semi-painful.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs