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

Unknown macro: {spacejump}

or visit the latest FishEye documentation home page.

Opening the Administration Screen for JIRA Integration

To set up JIRA integration, open the Administration screen, then click JIRA Servers (under 'Global Settings' in the left navigation panel). 


On the 'View JIRA Servers' page, you can carry out a number of operations as described below.

Adding a New JIRA Server

To add a new JIRA server from the View JIRA Servers page, click Add JIRA Server.

A number of fields and options must be filled out or selected on this page. See the table below for information on each field.

Option

Type

Description

Required

Name

Text Field

A descriptive name for the JIRA server.

Yes

URL

Text Field

The base URL of the JIRA server, e.g.

http://jira.atlassian.com

 

Yes

Username

Text Field

The username of an account on the JIRA instance. (All activity that takes place will be attributed to this user, unless using the Trusted Application setting).

Yes

Password

Text Field

The password for the account on the JIRA instance.

Yes

Include in Activity Streams

Check Box

Allows JIRA information to appear in the Activity Streams.

No

Authenticate as Trusted Application

Check Box

Allows the system to interface with JIRA, letting users log on with their own accounts (and use their own accounts on the JIRA server). If you enable subtasks using a trusted JIRA instance, you will also need to add FishEye as a trusted application to your JIRA instance, and then add the root path (denoted by '/' ) to the URL Paths to Allow field on the trusted applications screen in the administration interface of your JIRA instance. For more information, see the FishEye documentation about trusted applications. Also see the Known Issues.

No

Subtask Type ID

Number

This is required to enable creating issues from a Crucible comment (not required for FishEye). See the instructions on obtaining this number.

No

Subtask Resolution Action ID

Number

This is required to enable creating issues from a Crucible comment (not required for FishEye). See the instructions on obtaining this number (not required for FishEye).

No

Subtask Resolution ID

Number

This is required to enable creating issues from a Crucible comment (not required for FishEye). See the instructions on obtaining this number (not required for FishEye).

No

Allow Unassigned

True/False Button

Allow unassigned sub-tasks. This setting must match your 'Allow Unassigned Issues ' setting in JIRA.

No

Once you've filled out the necessary fields, click 'Test' to ensure that your details are correct. If you have a positive message return from the test, click 'Save'.

Editing Default JIRA Server Mappings

(info) This setting has two effects; it enables the feature that shows JIRA information in a dynamic window when you hover the mouse over a JIRA issue key; it will also turn every issue key into a hyperlink to that issue.

To enable this feature, click Edit Default JIRA Server Mappings from the View JIRA Servers page. 


On this page, select the FishEye Repositories or Crucible Projects that you wish to associate with all the JIRA servers that you have configured for use in FishEye/Crucible. You can click add all to quickly include them all in this category. You can remove individual items by clicking the 'X' marks.

Once you've finished, click Save.

(warning) You should disable any existing Crucible linkers you have set up for JIRA, as they will override this feature and prevent the dynamic dialog box from appearing when you mouse over an issue.

Operations on Existing Servers

Once you have configured an existing JIRA server, there are three main operations you can carry out on it: Edit, Mappings and Delete. These options appear on the far right of the screen.


Edit settings for an existing JIRA server

Click Edit to adjust any of the general settings you configured when you first added the server.

Edit mappings for an existing JIRA server

Click Mappings to choose mappings only for that specific JIRA server.

Delete an existing JIRA server

Click Delete to remove the server from the list.

  • No labels