Crucible review showing all changesets instead of the ones selected

[Chnikki]

I created a review selecting only the changesets from revisions I made to a file. My team is in the middle of making a lot of revisions to the same file so we are committing our code in increments. It's easier to merge everything in bite size pieces.

In the review, not only are my revisions showing, but also every revision my team has made to the same file. Is there a way to only show the revisions I made to the file? Or is there a way to remove revisions from a review when viewing a file diff?

Crucible 2.8 m1

JIRA 5.0.6

SQL Server 2008

[John Werner · Accepted solution]

I feel your pain. We have also had a few reviews where two different people have been working concurrently in the same file and conducting two separate reviews of just their changes. (Our process wants to track changes and reviews thereof to specific bug reports.) Since you are reviewing revisions of the file, both sets of changes can and will be caught.

What one of our developers did notice is in some cases if you floated the mouse of the change and it wasn't part of the review, a message would come up saying something like "this change not explicitly in this review."

When I looked up to make sure I remembered it correctly, I found this feature request logged for Crucible: "Imrpove Diff functionality". In there is are some good tips, including what looks like might be a good GreeseMonkey script to "make "non-author" implicit lines grey - changes by the same user will still be green."

[Chnikki]

Thank you for the tips and link to CRUC-5690! I voted for it and I'm going to try the GreaseMonkey script.

[Chnikki]

Go to Add Content, Browse Changesets, search for your changes, only select the changesets you made.

[Alexander Taler]

If other team members committed changes between yours, then there isn't a way to show just your changes in a single review. You could either create separate reviews for each of your changes.

Excluding changes is a difficult problem to solve in the general case, which is probably why it's not supported.