Jira Data Center
Last updated
Last updated
The Jira Data Center integration allows Sleuth to use Jira Data Center as a deployment issue tracker. When you deploy, Sleuth will automatically connect your Jira Data Center issues to the deploys, so you can always find the source of your changes later. Direct links to related Jira Data Center projects are provided in the deploy cards, allowing you to quickly see the Jira issues that affect your deploys.
Integration with Jira Data Center is made at the Sleuth organization level. More than one issue tracker can be integrated with an organization. Although you can have multiple projects within an organization, each project can only configured to use a single issue tracker. Bitbucket, due to its own integration with Jira Data Center, can be used as one of those since Bitbucket can automatically connect to your Jira Data Center issues as long as both of those Atlassian products are both logged in with the same account. Bitbucket can also serve as a code deployment source change.
Once Jira Data Center is configured as the issue tracker, every time the Jira issue key is included in a deploy's commit message, Sleuth will automatically link that deploy with the corresponding issue in Jira Data Center.
Check out the Sleuth for Jira integration in the Atlassian Marketplace.
To set up the Sleuth Jira Data Center integration:
Click Integrations in the left sidebar, then click Issue Trackers.
In the Jira Data Center tile, click enable.
Enter the URL of your Jira instance. If you want to authenticate via a Personal Access Token, enter that or if you want to authenticate with a username and password, enter those into the corresponding fields, then press Save.
If you using Jira Date Center on-premise behind Cloudflare access or similar, Sleuth might need to include some HTTP headers in order to reach your instance. In order to set Sleuth to send any custom HTTP headers when making requests:
In the Jira Data Center dialog, click on the Advanced setting
Enter comma separated list of custom headers you want Sleuth to include
The message Jira enabled is displayed in the tile.
After setting up the Jira Data Center integration, you must designate which Sleuth project to use as the default issue tracker. If you are configuring the integration immediately after setting it up, you can go directly to step #2 below.
Click on Integrations in the left sidebar, then on Issue Trackers.
Click on the Jira Data Center Set default issue tracker dropdown (see screenshot above).
All projects in the organization are displayed. Select which project you'd like to set Jira Data Center as the default issue tracker for.
You can also change the default issue tracker at any time.
Click on Project Settings in the left sidebar, then select Details.
Press Save.
Click on Integrations in the left sidebar, then on Issue Trackers.
Click disable. The message Jira disabled is displayed in the Jira Data Center integration card once the integration is dissolved.
The Jira Data Center integration is disconnected and no longer available to any projects within that organization. Any projects that used the Jira Data Center integration will need a new default issue tracker selected.
Click on Project Settings in the left sidebar, then select Details.
Select a new default issue tracker. The integration must be connected via the organization before it's displayed here.
Press Save.
The Jira Data Center integration is disconnected and no longer available to any projects within that organization. You will need to select a new default issue tracker for any projects that used the Jira Data Center integration. Simply follow the instructions in the section above: To set a new default issue tracker.
Select a new default issue tracker. The integration must be connected at the organization level before it can be selected.
