[FishEye ナレッジ ベース]
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.
Smart commits that transition JIRA issues require the following:
A project/entity link between FishEye/Crucible and JIRA is required for JIRA versions earlier that JIRA 5.0, with JIRA FishEye Plugin versions earlier than 5.0.10. See Adding project links between applications.
If the Application Link is configured as OAuth
If the Application Link to JIRA is configured to use OAuth, the commiting user must authenticate with JIRA before any smart commit will work with JIRA. Accomplish this by the following instructions:
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.
To disable Smart Commits, deselect the checkboxes for all types of Smart Commit.
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.