Linking to another application
Linking two Atlassian applications, for example Crucible and Jira Software, allows you to access one application's functions and resources from within the other. You link two applications by creating an application link between them.
See Jira integration in Crucible for an overview of the benefits of integrating your Atlassian applications with Crucible.
When linking an Atlassian Cloud instance to Crucible, your Crucible application must be accessible through port 80 (or port 443 with a valid (CA) SSL certificate). See these pages for more information:
To link two Atlassian applications:
- Click the 'cog' menu in the Crucible header, and choose Administration (you'll need to be logged in as an administrator to see this link).
- Choose Application Links in the left-hand panel. The Application Links configuration page displays links that have already been set up.
- Enter the URL of the application you want to link to, then click Create new link.
- If you check The servers have the same set of users... then this link will be configured using OAuth (with impersonation) authentication.
- If you are not an admin on both servers you won't be able to set up a 2-way (reciprocal) application link. If you want to go ahead and create a 1-way link anyway, clear the I am an administrator on both instances checkbox.
- Use the wizard to finish configuring the link.
When you complete the wizard, the application links plugin will create the link between your applications using OAuth authentication. After the link has been set up, it will appear on the Application Links configuration page. You can use that page to edit the configuration of application links:
- To edit the settings of an application link (for example, to update the authentication type of the link), choose the pencil icon on the right.
- For Crucible 4.2 and later, the application links plugin provides instant visibility into integration status, and focused diagnostics for when things stop working. See Application links diagnostics for details.
- For Crucible 4.2 and later, an application link will only use OAuth or OAuth (with impersonation) authentication. However, legacy application link authentication types (that is, Trusted Applications or Basic Access authentication) will continue to work after updating from older versions of Crucible. You can easily migrate legacy authentication types to the supported OAuth type - see Update application links to use OAuth for more details.
- Only use the OAuth (with impersonation) authentication option when configuring an application link if your servers both have the same set of users and they fully trust each other.
Having trouble integrating your Atlassian products with application links?
We've developed a guide to troubleshooting application links, to help you out. Take a look at it if you need a hand getting around any errors or roadblocks with setting up application links.
Was this helpful?Yes Provide feedback about this article