Connect Azure Boards
Connect the work items of Azure DevOps with a token for work items, and its service hooks.
In short
Connect Azure Boards once for the whole organization. Boards then keep their cards in step with an Azure DevOps project through it.
Before you start
- Who: someone who may manage the organization's connections - owners and admins have it by default.
- Plan: Jira and Azure Boards come with a paid plan, and the 14-day Business trial has them.
- First: an Azure DevOps account that can change work items, and the Project Administrator role to add service hooks.
Where it lives
- Open your organization, then Settings › "Connections", and press "Connect a work tracker".
- Choose "Azure Boards". The wizard opens; each step is checked before the next one opens.
- Choose "Azure DevOps Services" and type the "Organization", or choose "Azure DevOps Server" and type its "Address".
- Press "Check this step".
Sign in
- Press "Open the token page". Azure DevOps opens Personal access tokens.
- Press New Token, choose Custom defined under Scopes, tick Work Items: Read and write, and press Create.
- Copy the token, paste it into "Token".
- Type one project name into "A project to check with", such as Payments.
- Press "Check this step": it signs in and reads it.
Webhook
The webhook tells {{brand}} the moment something changes in Azure DevOps, so nothing waits for the next read.
- Press "Make the address and secret". Copy each with "Copy address" and "Copy secret" - the secret is shown only now.
- In Azure DevOps, open the project, then Project settings, Service hooks, Create subscription, Web Hooks.
- Choose Work item created. Make the same subscription for Work item updated, deleted and restored.
- Paste the address as the URL. Under HTTP headers paste the line "Copy header" copied.
- Press Test to send a first delivery, then Finish.
- Back in the wizard, press "Look for a delivery". You can also go on with "Next"; deliveries show up under "Deliveries".
Check and use
- Press "Run the full check". Every step should say Passed; a step that failed names what to change.
- Under "Where will you use it?" tick Boards.
- Optional: under "Only these teams" tick the teams that may pick it. Leave it empty for everyone who may use those modules.
- 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
- A board picks the area and iteration it syncs when it uses the connection; the connection itself is the whole organization.
- 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