Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Crucible: My users are whining -- I need answers to "a failed review"

I've been getting my users to play with Crucible/Fisheye so we can coming up with a common inspection process. They have questions -- I need answers:

2/ A designer will setup the review but his manager and those involved in the review want to know if the comments made in the review have been addressed?
- what constitutes a failed review and how would it show up in Crucible?
- simply knowing that your comment has been read, does not constitute that it has been resolved.
- I know I can "flag" a comment as a Defect and I can probably create another Jira issue from that flagged Defect but I don't want to. I already have a Jira defect issue opened for this review/code submission so I don't want to open more issues when the code hasn't been formally submitted yet.
- how do others handle this situation?

1 answer

0 votes

Hi Brent,

As can be seen here, a review cannot be flagged as "failed" because there is no such review state in the Crucible workflow

 However, if a comment on a review is flagged as "Defect" and a JIRA issue has been created based on it, it can be understood that problems have been detected in the source code being reviewed, hence the review can be considered as "failed".

The outcome of the new JIRA issue will be a new commit with the necessary changes to fix the problem and close the JIRA issue, and a new review should be created for this new changeset committed, and this review will follow the same workflow as the previous one.

Kind regards,
Felipe Kraemer

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

398 views 19 23
Read article

Community Events

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

Events near you