source-code-anlysis-issue.jpgThis is the second of a three part blog series on JIRA integration. In part 1 of the series we started off discussing the value of linking issues and code reviews, we now move on to relating source code to your issues.

Source Code and Issues

Open up any development toolbox and you are guaranteed to find two things – an issue tracker and a source code management tool (SCM). Your issue tracker is keeping tabs on the work being done and your SCM is the actual work getting done.
Integrating these tools will give you a full view of how your source code is affecting the progress of the projects you are working on.
JIRA can integrate with Atlassian’s FishEye to give you visibility into your Subversion, Perforce, CVS, GIT or Clearcase repository.

Integrate JIRA and FishEye

Watch the video below to see how integrating JIRA and FishEye can help you understand the source that is affecting your issues.

  • Visibility into the source code that is associated with your JIRA issues – the FishEye plugin gives you visibility into your source repository through JIRA – see source and changes in your code at the project and issue level.
  • Activity Streams – streams show a user’s activity in your SCM along with all related activities in JIRA and Crucible. RSS feeds allow you to display this information in your preferred reader or in other places like Confluence.
  • Cross linking between JIRA and FishEye – there is no context switching when using JIRA and FishEye. One click in JIRA can take you directly into any changeset, view diffs, or jump to fully annotated source in FishEye. FishEye provides detailed information on issues related to a changeset.


Leave a comment and let us know how you are using JIRA with your source code.

Fresh ideas, announcements, and inspiration for your team, delivered weekly.

Subscribe now

Fresh ideas, announcements, and inspiration for your team, delivered weekly.

Subscribe now