Documentation for FishEye 3.0.x. Documentation for other versions is available too.

Because Git and Mercurial allow commits to be attributed to users other than those pushing changes to the repository, if your FishEye instance has any DVCS repositories then Smart Commits will be disabled. This is a security measure to prevent privilege escalation. This only occurs when the feature is first initialised, and will not be disabled if new Git or Mercurial repositories are added afterwards.

Requirements

Smart commits making use of JIRA issue transitioning requires at least version 3.4.5 of the JIRA FishEye plugin. It can be downloaded via the Atlassian plugin manager from within JIRA or manually downloaded from the Atlassian plugin exchange.

Note that Smart Commits also require the following:

 

On this page:

Related pages:

Enabling Smart Commits

To enable smart commits, open the FishEye Administration interface and go to the Smart Commits configuration page.

Select the Smart Commits that you would like to enable.

Disabling Smart Commits

To disable Smart Commits, deselect the checkboxes for all types of Smart Commit.

FAQ

Q. The Smart Commits administration page is reporting an error, saying "No plugins installed"

A. It is possible that the smart commit plugins are disabled in the Plugins section of your FishEye instance. Please navigate to System Settings > Plugins and open System Plugins. Please ensure that the FishEye/Crucible Review Smart Commit Plugin and FishEye/Crucible JIRA Smart Commit Hook Plugin are enabled (as well as all of their submodules). If you are unable to enable them, please view your FishEye logs for clues and raise a support request at http://support.atlassian.com/ with your logs attached.

  • No labels

 

 

 Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.