Connect Jira Data Center

Connect your own Jira server with a personal access token, and its webhook.

In short

Connect your own Jira once for the whole organization. Boards then keep their cards in step with a Jira project through it.

Before you start

• Who: someone who may manage the organization's connections - owners and admins have it by default.
• Plan: your own Jira comes with the Enterprise plan.
• First: a Jira account that can see the projects, and Jira admin rights to add a webhook.

Where it lives

1. Open your organization, then Settings › "Connections", and press "Connect a work tracker".
2. Choose "Jira Data Center". The wizard opens; each step is checked before the next one opens.
3. Type the "Address" you open Jira at, such as https://jira.example.com, and press "Check this step".

Sign in

1. Press "Open the token page". Jira opens your profile's Personal Access Tokens.
2. Press Create token, give it a name and an expiry date, and copy it.
3. Paste it into "Token".
4. Type one project key into "A project to check with", such as PAY.
5. Press "Check this step": it signs in and reads it.

Webhook

The webhook tells {{brand}} the moment something changes in Jira, so nothing waits for the next read.

1. Press "Make the address and secret". Copy each with "Copy address" and "Copy secret" - the secret is shown only now.
2. In Jira, open Administration, System, WebHooks, Create a WebHook.
3. Paste the address as the URL and the secret as the Secret.
4. Tick Issue created, updated and deleted. A JQL filter can limit it to your projects.
5. Press Create, then change an issue to send a first delivery.
6. Back in the wizard, press "Look for a delivery". You can also go on with "Next"; deliveries show up under "Deliveries".

Check and use

1. Press "Run the full check". Every step should say Passed; a step that failed names what to change.
2. Under "Where will you use it?" tick Boards.
3. Optional: under "Only these teams" tick the teams that may pick it. Leave it empty for everyone who may use those modules.
4. Check the "Name" - boards, designs and projects show it - and press "Finish". The connection shows under "Connections" with its health.

If a step fails

• A failed step names its code, what it means and what to change. The code's section of /help/settings/fix-a-company-connection says more.
• Change what the step says and press "Check again". The next step opens only when this one passes.
• Closing the wizard keeps every step that passed. Press "Continue setup" on the connection's row to go on where you stopped.

Good to know

• If a firewall protects your Jira, allow the addresses the check names in its fix.

• A connection's row shows its health, its last delivery and "Where used".
• "Deliveries" lists what the webhook address received in the last 30 days and where each delivery went.
• "Disconnect" first lists every board, design and project that would stop using it.
• Nobody else pastes a token: boards, designs and API projects pick this connection.

Related

• /help/settings/connect-jira-cloud
• /help/settings/fix-a-company-connection
• /help/settings/webhooks-and-site-ownership