JIRA is Atlassian's issue tracking and project management application.

See JIRA integration in Crucible for a description of all the integrations you get when Crucible is linked with JIRA.

This page describes how to integrate JIRA with Crucible.

When Crucible was first installed, JIRA integration may have been configured using the setup wizard, which configures the JIRA connection automatically for user management. See Configuring JIRA integration in the Setup Wizard.

However, JIRA integration with Crucible can be configured at any time after installation, as described on this page.

Initial configuration in JIRA

Configure the following setting in each instance of JIRA that you wish to link to Crucible:

Consider also the following, to make full use of the integration between Crucible and JIRA:

On this page:

Related pages:

Linking Crucible with JIRA instances

You can integrate Crucible with one or more instances of JIRA from the Crucible administration area. There are two parts to integrating with a JIRA instance:

Configuring an application link with JIRA

This section describes how to create a two-way applications link between Crucible and JIRA. Please refer to Adding an application link for information about the various options available.

To create a new application link between Crucible and JIRA:

  1. Go to your Crucible administration screen and click Application Links (under 'Global Settings').
  2. Enter the URL for the JIRA instance you want to link to and click Create new link.
  3. Complete the application link wizard to connect Crucible to your JIRA server. You must make use of the automatic link-back from JIRA to Crucible to get full integration (you'll need the JIRA system administrator global permission for that).

 

For FishEye 3.2 and later, creating a new application link now uses OAuth by default and enables both 3-legged OAuth (3LO) and 2-legged OAuth (2LO).


To update an existing application link with JIRA:

When you update an older application link to use OAuth, 3-legged authentication is applied by default. However, you'll need to explicitly enable 2-legged authentication in order to see Crucible information in the JIRA Development panel (when integrated with JIRA 6.2 or later).  Enable 2LO for the application link as follows:

  1. Go to the Crucible admin area and click Add-ons > Application Links.
  2. Click Edit for the app link with JIRA.
  3. For both Outgoing Authentication and Incoming Authentication:
    1. Click OAuth
    2. Check Allow 2-legged OAuth.
    3. Click Update.

The application link update process will involve you logging into JIRA for a short time to configure the JIRA end of the link, before returning you to the Crucible.

Connecting to JIRA for user management

This option is available only with JIRA 4.3 and later.

To manage your Crucible users using JIRA, configure a connection in JIRA and then set up the user directory in Crucible. Both steps are described below.

To configure a new connection for user management in JIRA:

  1. Log in to JIRA as a user with the 'JIRA System Administrators' global permission.
  2. Click Administration on the JIRA top navigation bar. 

To set up the JIRA user directory in Crucible:

Go to your Crucible administration screen. 

Inline issue creation

Inline issue creation allows a user to create a JIRA issue from a review comment. The user must have the 'Comment' permission in Crucible to see the Create Issue link in the comment. See Creating JIRA issues from the review.

This requires that Crucible is integrated with JIRA 5.0, or later, and is disabled if Crucible is integrated with an earlier version of JIRA.

When creating the issue, the Create Issue dialog only displays required fields for the selected issue type.

In the new issue in JIRA, you see a link back to the comment in Crucible. However:

You can disable the Inline Issue Creation plugin in Crucible to restore the earlier behaviour.