Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Connect to Jira - Server

  • On Confluence Server, Custom Charts will automatically link to the Primary Jira connected to the Confluence instance.

  • Only the Primary Jira will be used and it is currently not possible to select an alternative if multiple Jira instances are connected to Confluence. If you require this additional functionality please contact our support team to discuss this feature.

  • Custom Jira Charts for Confluence Server & Data Center can only be used with Jira Server & Data Center instances.

  • Jira must be connected to Confluence using OAuth (impersonation) and the usernames must match exactly on both instances for Custom Charts to function as expected.

  • A detailed description (with screenshots) of how to correctly configure the application links can be found here in the section below

Custom Jira Charts for Confluence on Server requires OAuth (impersonation) to be enabled to access Jira data. This application link type is required to use Custom Jira Charts for Confluence. This is required because it ensures that user information matches between Jira and Confluence. If a user’s information is even slightly different in Jira and Confluence, the charts will not work for them. If OAuth (without impersonation) is used, some or all users in your Confluence instance may be unable to view Custom Charts.

If you have two Jira instances connected to Confluence only the Primary Jira instance will be used.

For more information on the difference between OAuth and OAuth (Impersonation), see this article from Atlassian: ​OAuth security for application links | Application Links Data Center and Server 9.0 | Atlassian Documentation

Application Link Configuration

Step 1: On Confluence, as an administrator, navigate to General configuration → Application Links.

Step 2: Edit the Jira application link and set both Outgoing and Incoming local authentication methods to OAuth (impersonation).

Step 3: Save changes once both authentication options have been updated.

Step 4: When both Outgoing and Incoming local authentication methods have been set to OAuth (impersonation), navigate to Jira Application Links (using the link under Remote authentication) and perform the same actions again on the reciprocal link from Jira.

Note: The ​CONFIG ERROR status is expected because you haven't yet updated the reciprocal link from Jira to Confluence.

Step 5: Save changes once both local authentication options have been updated.

Once both application links have been updated on Jira and Confluence you should see the status return to ​CONNECTED

 

And that's it! You can return to your Confluence page and start using the Custom Jira Charts for Confluence macro ​Emoji :slight_smile:

  • No labels