Viewing the Commit Graph for a Repository

The commit graph shows changesets in their respective branches, using configurable "swimlanes". This allows you to see key information such as branching and merging (if you are using Git or Mercurial, you will be able to see anonymous branches as well). You can also use highlights to identify changesets in the same branch, commits with JIRA issues, and reviewed/unreviewed changesets. Clicking a changeset with the appropriate highlight active shows you related changesets, such as changesets with the same lineage, the same JIRA issue or same Crucible review.

On this page:

Before You Begin

The commit graph is not supported for ClearCase repositories.
Subversion repositories currently do not show lines between branch swimlanes (i.e. merging).
Some features of the commit graph are only available if you are using Crucible with FishEye. For details, see the description below.
Some features of the commit graph are only available if you are using JIRA with FishEye. For details, see the description below.

Browsing to the Commit Graph for a Repository

To view the commit graph for a repository:

Navigate to the desired repository, as described on Browsing through a Repository.
Click the 'Commit Graph' tab.
The commit graph for the repository will be displayed. Annotated screenshot above: Commit graph for a repository – default view

Highlighting Information in the Commit Graph

The 'Highlight' dropdown of the commit graph allows you to highlight different types of information in the swimlanes. When a highlight is active, you can also select a changeset in the changeset list to show related changesets. For example, if you have the 'JIRA Issues' highlight active, selecting a changeset with a JIRA issue (in the commit comment) will show which other changesets have the same JIRA issue.

Selecting a changeset (regardless of highlight) will display the following in the changeset list:

Display an icon next to the changeset. Clicking this changeset will display a changeset summary
Display dropdown menu (accessible via a cog icon) allowing you to view the full changeset, view the changeset in the activity stream or create a review for the changeset.

In this section:

Highlighting the Lineage of a Changeset
Highlighting JIRA Issues
Highlighting Reviewed Changesets

Highlighting the Lineage of a Changeset

Action	Behaviour
Select the 'Lineage' highlight	Colours the changesets in the swimlanes according to which branch they are in.
Select a changeset in the changeset list with the 'Lineage' highlight active	Shows where a changeset comes from and where it propagates to, i.e. its ancestors and descendants.
Mouseover a changeset in the swimlanes with the 'Lineage' highlight active	Shows a pop-up displaying all branches that the changeset is referenced in. This will include branches that you may not have swimlanes displayed for.

Screenshot: Commit graph with the 'Lineage' highlight active (with mouseover on a changeset)

Highlighting JIRA Issues

This highlight is only available if you have integrated FishEye with JIRA and linked your repository to a JIRA project.

Action	Behaviour
Select the 'JIRA issues' highlight	Colours the changesets in the swimlanes that have a JIRA issue key in the commit message.
Select a changeset in the changeset list with the 'JIRA issues' highlight active	Colours the changesets in the swimlanes that have the same JIRA issue key in the commit message, as the changeset selected.
Mouseover a changeset in the swimlanes with the 'JIRA issues' highlight active	Shows a pop-up displaying all branches that the changeset is referenced in and all referenced JIRA issues.

Screenshot: Commit graph with the 'JIRA Issues' highlight active (with mouseover on a JIRA issue key)

Highlighting Reviewed Changesets

This highlight is only available if you are using FishEye with Crucible.

Action	Behaviour
Select the 'Reviewed changesets' highlight	Colours the changesets in the swimlanes that have been reviewed (i.e. included in a Crucible review), as follows: * Red dot: Unreviewed changeset, i.e. associated with review in 'Dead' or 'Rejected' state or no review associated. * Yellow dot: Changeset under review, i.e. associated with review not in 'Dead', 'Rejected' or 'Closed' state. * Green dot: Changeset reviewed, i.e. associated with review in 'Closed' state.
Select a changeset in the changeset list with the 'Reviewed changesets' highlight active	Colours the changesets in the swimlanes that are part of the same review as the changeset selected.
Mouseover a changeset in the swimlanes with the 'Reviewed changesets' highlight active	Shows a pop-up displaying all branches that the changeset is referenced in and the Crucible review key.

Screenshot: Commit graph with the 'Reviewed changesets' highlight active (with mouseover on a changeset)

Viewing Changesets Across All Branches

The 'All Branches' mode allows you to view commit activity across all branches of a repository. In this mode, the swimlane headers are not displayed. However, you can mouseover any changeset to display information about the changeset, as described in the 'Highlighting Information in the Commit Graph' section above.

To view the 'All Branches' mode of the commit graph for a repository:

Click the 'select branches...' button when viewing the commit graph.
In the 'Select Branches' pop-up, click 'Switch to all branches mode'.

Screenshot: Commit graph – 'All Branches' mode.

Reordering Swimlanes for Git Repositories

Reordering swimlanes is useful if you just want to show branches in a certain order. However, ordering swimlanes is vital for Git repositories, as it is the only way of determining which branch a commit is from.

When you view the commit graph for a Git repository, FishEye works from the leftmost swimlane to the right doing the following:

For each swimlane, FishEye checks if the commit is in that branch. If the commit is in the branch, a dot is shown representing the commit.
If the commit is not in the branch, the dot for the commit is moved to the next column on the right.

For example, if the 'master' swimlane is to the left of another swimlane, e.g. 'fisheye-2.6' branch, there will be no changesets shown in the 'fisheye-2.6' swimlane, as all the commits will be picked up in the 'master' swimlane. However, if you move the 'fisheye-2.6' swimlane to the left of the 'master' swimlane, it will pick up all of the FishEye 2.6 commits.

For more information, read this Knowledge Base article: Ordering of Branches Important When Visualising Git Changesets

All Versions

FishEye 2.6 Documentation

Child pages