This is the documentation for FishEye 3.6. View the latest version of

Unknown macro: {spacejump}

or visit the latest FishEye documentation home page.

Skip to end of metadata
Go to start of metadata

JIRA is Atlassian's issue tracking and project management application – when FishEye is integrated with JIRA, you and your team get all the benefits described on this page. Go straight to Linking FishEye to JIRA if you want to connect FishEye to a JIRA server.

You can also use JIRA for delegated management of your FishEye users. See JIRA and Crowd Authentication.

See Streamlining your development with JIRA for the full story of how Atlassian tools work together to give you a fast and guided software development process.

Starting in JIRA 6.2.2 the Source and Reviews tabs are only displayed if JIRA is unable to display the associated information in the Development Tools panel.


Your user tiers don't need to match between JIRA and FishEye/Crucible in order to integrate them. JIRA users that are not FishEye users will see the same view as FishEye users within JIRA, but will not be able to log in to FishEye to view the source/reviews.

See in JIRA the FishEye repository branches related to an issue

FISHEYE 3.3+ JIRA 6.2+

For FishEye 3.3 and later, the FishEye repository branches related to a JIRA issue are summarized in the Development panel for the issue, when JIRA and FishEye are connected with an application link. To see details of the branches, simply click the branches link. You can see which repository each branch is in and when the last commit was made. As long as the issue key is included in the branch name the branch is automatically linked to the JIRA issue.

 

See in JIRA the commits related to an issue

FISHEYE 3.3+ JIRA 6.2+

For FishEye 3.3 and later, the FishEye repository commits related to a JIRA issue are summarized in the Development panel for the issue, when JIRA and FishEye are connected with an application link. You can click the commits link to see detailed information such as who made each commit, when they commited, and how many files were changed. Click through to see a particular commit in the FishEye instance where the commit was made. A developer only needs to add the issue key to the commit message for that commit to be automatically linked to the JIRA issue.

 

See the JIRA issues related to commits

FISHEYE 3.1+

FishEye recognises JIRA issue keys, and displays those as links in places such as the activity stream, side-by-side diffs, and commit messages:

Click on the linked issue key to see details for the issue, as described next.

 

See the details for JIRA issues

FISHEYE 3.1+

Click a linked issue key anywhere in FishEye to see the details of that issue in a dialog. And you can click the issue key at the top of the dialog to go straight to the issue in JIRA:

 

Transition JIRA issues from within FishEye

FISHEYE 3.1+ 

You can easily transition a JIRA issue from within FishEye. For example, when viewing a commit, you may want to transition the related JIRA issue into QA. Click on a linked JIRA issue anywhere in FishEye to see a dialog with the available workflow steps:

Click on a step in the dialog, and complete any displayed fields as required. If there are custom required fields that are unsupported by FishEye, just click Edit this field in JIRA to transition the issue directly in JIRA.

 

See issues from multiple instances of JIRA

FISHEYE 3.1+ 

FishEye can link to more than one JIRA server at a time, so different teams can work with their own projects in different JIRA instances, or a single team can link to issues across multiple JIRA servers.