Configuring JIRA integration in the Setup Wizard

Solution 1: Removing a Partial Configuration – The Easiest Way

If the application's setup wizard fails part-way through setting up the JIRA integration, you may need to remove the partial configuration from JIRA before continuing with your application setup. Please follow the steps below.

Remove the partial configuration if it exists, try the 'Connect to JIRA' step again, and then continue with the setup wizard:

1. Log in to JIRA as a user with the 'JIRA System Administrators' global permission.
2. Click the 'Administration' link on the JIRA top navigation bar.
3. Remove the application link from JIRA, if it exists:
   1. Click Application Links in the JIRA administration menu. The 'Configure Application Links' page will appear, showing the application links that have been set up.
   2. Look for a link to your application. It will have a base URL of the application linked to JIRA. For example:
      
      • If you want to remove a link between JIRA and FishEye, look for the one where the Application URL matches the base URL of your FishEye server.
      • If you want to remove a link between JIRA and Confluence, look for the one where the Application URL matches the base URL of your Confluence server.
      • If you want to remove a link between JIRA and Stash, look for the one where the Application URL matches the base URL of your Stash server.
   3. Click Delete next to the application link that you want to delete.
   4. A confirmation screen will appear. Click Confirm to delete the application link.
4. Remove the user management configuration from JIRA, if it exists:
   1. Go to the JIRA administration screen for configuring the applications that have been set up to use JIRA for user management:
      • In JIRA 4.3: Click 'Other Applications' in the 'Users, Groups & Roles' section of the JIRA administration screen.
      • In JIRA 4.4: Select 'Administration' > 'Users' > 'JIRA User Server'.
   2. Look for a link to your application. It will have a name matching this format:

      <Type> - <HostName> - <Application ID> 
      

      For example:

      FishEye / Crucible - localhost - 92004b08-5657-3048-b5dc-f886e662ba15
      

      Or:

      Confluence - localhost - 92004b08-5657-3048-b5dc-f886e662ba15
      

      If you have multiple servers of the same type running on the same host, you will need to match the application ID of your application with the one shown in JIRA. To find the application ID:
      • Go to the following URL in your browser:

        <baseUrl>/rest/applinks/1.0/manifest
        

        Replace <baseUrl> with the base URL of your application.
        For example:

        http://localhost:8060/rest/applinks/1.0/manifest
        

      • The application links manifest will appear. Check the application ID in the <id> element.
   3. In JIRA, click 'Delete' next to the application that you want to remove.
5. Go back to the setup wizard and try the 'Connect to JIRA' step again.

Solution 2: Removing a Partial Configuration – The Longer Way

If solution 1 above does not work, you may need to remove the partial configruration and then add the full integration manually. Please follow these steps:

1. Skip the 'Connect to JIRA' step and continue with the setup wizard, to complete the initial configuration of the application.
2. Log in to JIRA as a user with the 'JIRA System Administrators' global permission.
3. Click the 'Administration' link on the JIRA top navigation bar.
4. Remove the application link from JIRA, if it exists:
   1. Click Application Links in the JIRA administration menu. The 'Configure Application Links' page will appear, showing the application links that have been set up.
   2. Look for a link to your application. It will have a base URL of the application linked to JIRA. For example:
      
      • If you want to remove a link between JIRA and FishEye, look for the one where the Application URL matches the base URL of your FishEye server.
      • If you want to remove a link between JIRA and Confluence, look for the one where the Application URL matches the base URL of your Confluence server.
      • If you want to remove a link between JIRA and Stash, look for the one where the Application URL matches the base URL of your Stash server.
   3. Click Delete next to the application link that you want to delete.
   4. A confirmation screen will appear. Click Confirm to delete the application link.
5. Remove the user management configuration from JIRA, if it exists:
   1. Go to the JIRA administration screen for configuring the applications that have been set up to use JIRA for user management:
      • In JIRA 4.3: Click 'Other Applications' in the 'Users, Groups & Roles' section of the JIRA administration screen.
      • In JIRA 4.4: Select 'Administration' > 'Users' > 'JIRA User Server'.
   2. Look for a link to your application. It will have a name matching this format:

      <Type> - <HostName> - <Application ID> 
      

      For example:

      FishEye / Crucible - localhost - 92004b08-5657-3048-b5dc-f886e662ba15
      

      Or:

      Confluence - localhost - 92004b08-5657-3048-b5dc-f886e662ba15
      

      If you have multiple servers of the same type running on the same host, you will need to match the application ID of your application with the one shown in JIRA. To find the application ID:
      • Go to the following URL in your browser:

        <baseUrl>/rest/applinks/1.0/manifest
        

        Replace <baseUrl> with the base URL of your application.
        For example:

        http://localhost:8060/rest/applinks/1.0/manifest
        

      • The application links manifest will appear. Check the application ID in the <id> element.
   3. In JIRA, click 'Delete' next to the application that you want to remove.
6. Add the application link in JIRA again, so that you now have a two-way trusted link between JIRA and your application:
   1. Click Add Application Link. Step 1 of the link wizard will appear.
   2. Enter the server URL of the application that you want to link to (the 'remote application').
   3. Click Next.
   4. Enter the following information:
      • Create a link back to this server – Check to add a two-way link between the two applications.
      • Username and Password – Enter the credentials for a username that has administrator access to the remote application.
        Note: These credentials are only used to authenticate you to the remote application, so that Application Links can make the changes required for the new link. The credentials are not saved.
      • Reciprocal Link URL – The URL you give here will override the base URL specified in your remote application's administration console, for the purposes of the application links connection. Application Links will use this URL to access the remote application.
   5. Click Next.
   6. Enter the information required to configure authentication for your application link:
      • The servers have the same set of users – Check this box, because the users are the same in both applications.
      • These servers fully trust each other – Check this box, because you trust the code in both applications and are sure both applications will maintain the security of their private keys.
        For more information about configuring authentication, see Configuring authentication for an application link.
   7. Click Create.
7. Configure a new connection for user management in JIRA:
   1. Go to the JIRA administration screen for configuring the applications that have been set up to use JIRA for user management:
      • In JIRA 4.3: Click 'Other Applications' in the 'Users, Groups & Roles' section of the JIRA administration screen.
      • In JIRA 4.4: Select 'Administration' > 'Users' > 'JIRA User Server'.
   2. Add an application.
   3. Enter the application name and password that your application will use when accessing JIRA.
   4. Enter the IP address or addresses of your application. Valid values are:
      • A full IP address, e.g. 192.168.10.12.
      • A wildcard IP range, using CIDR notation, e.g. 192.168.10.1/16. For more information, see the introduction to CIDR notation on Wikipedia and RFC 4632.
      • Save the new application.
8. Set up the JIRA user directory in the application.
   • For Confluence:
     1. Go to the Confluence Administration Console.
     2. Click 'User Directories' in the left-hand panel.
     3. Add a directory and select type 'Atlassian JIRA'.
     4. Enter the following information:
        • Name – Enter the name of your JIRA server.
        • Server URL – Enter web address of your JIRA server. Examples:

          http://www.example.com:8080/jira/
          http://jira.example.com
          

        • Application name and Application password – Enter the values that you defined for Confluence in the settings on JIRA.
     5. Save the directory settings.
     6. Define the directory order by clicking the blue up- and down-arrows next to each directory on the 'User Directories' screen.
        For details see Connecting to Crowd or Jira for User Management.
   • For FishEye/Crucible:
     1. Click Authentication (under 'Security Settings').
     2. Click Setup JIRA/Crowd authentication. Note, if LDAP authentication has already been set up, you will need to remove that before connecting to JIRA for user management.

     3. Make the following settings:
        
        

        Authenticate against	Select a JIRA instance
        Application name and password	Enter the values that you defined for your application in the settings on JIRA.
        JIRA URL	The web address of your JIRA server. Examples: http://www.example.com:8080/jira/ http://jira.example.com
        Auto-add	Select Create a FishEye user on successful login so that your JIRA users will be automatically added as a FishEye user when they first log in.
        Periodically synchronise users with JIRA	Select Yes to ensure that JIRA will synchronize all changes in the user information on a regular basis. Change the value for Synchronise Period if required.
        When Synchronisation Happens	Select an option depending on whether you want to allow changes to user attributes from within FishEye.
        Single Sign On	Select Disabled. SSO is not available when using JIRA for user management and if enabled will make the integration fail.

     4. Click Next and select at least one user group to be synchronised from JIRA. If necessary, you could create a new group in JIRA, such as 'fisheye-users', and select this group here.
     5. Click Save.
   • For Stash: 
     1. Go to the Stash administration area.
     2. Click User Directories in the left-hand panel.
     3. Add a directory and select type Atlassian JIRA.
     4. Enter the following information:
        
        • Name – Enter the name of your JIRA server.

        • Server URL– Enter web address of your JIRA server. Examples:

          http://www.example.com:8080/jira/
          http://jira.example.com
          

        • Application name and Application password – Enter the values that you defined for Stash in the settings on JIRA.
     5. Save the directory settings.
     6. Define the directory order by clicking the blue up- and down-arrows next to each directory on the 'User Directories' screen.
        For details see Connecting Stash to JIRA for user management.

Solution 3: Connecting FishEye and JIRA from JIRA instead of from the FishEye wizard

This is a workaround for the "Failed to create application link" errors on the FishEye wizard that connects to the JIRA instance.  You can try to set up the link from another side. 

1. Remove the partial configuration using Solution 1 or Solution 2
2. In FishEye, after logging in as a nameless administrator, manually create a user (left panel → User Settings → User → Add User); give him administrator rights (left panel → Security Settings → Administrators → move the user to the "Admin Users" column).
3. Go to the JIRA instance; Administration → Applications → Application links → Create link
   1. Enter the FishEye instance URL e.g. http://localhost:8060/
   2. Leave the checkbox saying the applications have the same set of users unchecked
   3. When redirected to FishEye, log in as the user created in (2).
4. The link should be created on both sides.