This is the first of three posts that will be released in the next several weeks covering the topic of JIRA integration with developer tools. Lets start the series off talking about code reviews and issues.
Code Review and Issues
Almost every software development team uses an issue tracker of some type, but few perform code reviews. Lets face it, code review is difficult.
For teams to adopt the practice of code review common hurdles need to be overcome:
- avoid disrupting developers
- avoid synchronization issues
- adopt process change
Atlassian Crucible code review tool alleviates these hurdles with a non-intrusive web based application that allows painless asynchronous code review with features like inline commenting, pre and post commit reviews and synchronization with Atlassian’s JIRA issue tracker.
In addition to better knowledge sharing and collaboration, one of the key outcomes of code review is identifying defects. Crucible allows you to identify the defects and integrate them into JIRA so you can take action before the bug reaches your customer.
Integrate JIRA and Crucible
Watch the video below to see how integrating JIRA and Crucible can help you improve your software quality.
- Initiate Crucible reviews from JIRA – initiate a review directly from JIRA with just one-click.
- Link comments as subtasks – When adding comments to a review, you can also create a corresponding subtask in the related JIRA issue with just one click.
- Resolve subtasks from Crucible – Once a comment and subtasks are linked, you can resolve them from either Crucible or JIRA and they’ll be updated in the other system as well. This means you don’t have to leave Crucible to update the status of your issues in JIRA.
- Review information about issues in Crucible and code reviews
in JIRA – Review comments are automatically incorporated into the
comments of the linked JIRA issue. There is also a Crucible tab which
includes all of the review details. JIRA issue details are available
in a review by just hovering over the issue key.