The document compares code review tools Bitbucket Pull Requests and Crucible. Bitbucket Pull Requests allow reviewers to comment on changes and discuss them with authors directly in the tool. Crucible provides more advanced review features like customizing reviews, viewing commit histories, and integrating with Jira. It also offers a formal review stage in the development process and reporting capabilities.

1. CODE REVIEW
Bitbucket pull
request vs crucible

2. Overall Flow

3. Bitbucket Pull request (Review process)
 Reviewers look through the diff to compare the changes with existing source code.
 Reviewers comment on changes and authors reply to comments, starting a discussion.
 Anyone can create a task based on a comment and authors resolve tasks as they complete them.
 Authors update code based on feedback and push new commits to the branch or fork, updating the pull
request.
 Authors check that all tests are passing on the most recent commit.
 Reviewers merge the pull request when satisfied with changes.

4. Crucible Overall Dashboard
Display recent activities, review items, repository &
projects

5. Review Dashboard
Display current review items with overall counts

6. All Branch activity
View all branch current activities using simple drop down

7. Repo Stats & filter
Complete commit stats for each repo with filter

8. Change-sets
threaded discussions with other user

9. Each commit &
branch review
File review
Even every single commit can
be review along with complete
branch
Every single file can be
review from commit

10. Review customization
Assign reviewer, set due date and reminder for all review

11. Iteration
Review status
Developer can view current
review progress
Complete iteration
view using drag button

12. Commit-Graph
Ancestors and descendants for a changeset/ commits with
Jira issues/ reviewed and unreviewed changesets

13. User activity &
stats
Complete commit history for each user

14. Report
Monitor repository activity in terms
of the number of lines of code
added and removed in a selected
period of time, and by selected
committers.

15. Report(cont.)
How much of the code, and which
files, in your repository have been
reviewed, and when

16. Advance Search
powerful search engine that allows you to find changesets, committers and files using search attributes

17. Pre-commit
 A patch file is a portion of a source code file that contains the code changes that we have made – it's a diff that shows the
differences between your working copy and the base revision.
 Once reviewed, the patch is either committed to the repository or is sent back to the author.
 Crucible patch anchoring feature helps us o see complete code changes.

18. Bitbucket integration
Main features:
• Integrate Crucible reviews into your pull request workflow to enforce a more stringent code review process.
• Block pull request merges that have not been reviewed in crucible
• Automatically create Crucible reviews for pull requests.

19. Jira integration
In Crucible, you can:
 See all the Crucible reviews related to a Jira Software issue
 Create a Crucible review directly from an issue in Jira Software
 Link your Crucible review to a Jira Software issue
 Create a Jira Software issue from a review comment
 Transition Jira Software issues automatically
 Transition Jira Software issues from within Crucible
 See issues from multiple instances of Jira Software
 See open reviews or unreviewed commits for an entire
version within Jira Software

20. Bitbucket pull-request vs Crucible
Crucible
Bitbucket
Pull request offer lightweight review
functionality with sophisticated policy
enforcement.
Crucible provide formal stage in our delivery lifecycle to
capture reviews. We can also browse, search and take
report via Fiisheye.