nodejs/hookshot
nodejs/hookshot
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-hookshot.git synced 2025-03-10 21:19:13 +00:00
Code Issues Packages Projects Releases Wiki Activity
hookshot/docs/setup/jira.md
Will Hunt 04eeb6f2d0 1.0.0
2021-12-21 17:18:15 +00:00

2.3 KiB
Raw Blame History

JIRA

Adding a webhook to a JIRA Organisation

This should be done for all JIRA organisations you wish to bridge. The steps may differ for SaaS and on-prem, but you need to go to the webhooks configuration page under Settings > System.

Next, add a webhook that points to / on the public webhooks address for hookshot. You should also include a secret value by appending ?secret=your-webhook-secret. The secret value can be anything, but should be reasonably secure and should also be stored in the config.yml file.

Ensure that you enable all the events that you wish to be bridge.

JIRA OAuth

The JIRA service currently only supports atlassian.com (JIRA SaaS) when handling user authentication. Support for on-prem deployments is hoping to land soon.

You will need a Atlassain account with the ability to use the developer tools in order to create the app.

You'll first need to head to https://developer.atlassian.com/console/myapps/create-3lo-app/ to create a "OAuth 2.0 (3LO)" integration.

Once named and created, you will need to: - Enable the User REST, Jira Platform REST and User Identity APIs under Permissions. - Use rotating tokens under Authorisation. - Set a callback url. This will be the public URL to hookshot with a path of /jira/oauth. - Copy the client ID and Secret from Settings

Configuration

You can now set some configuration in the bridge config.yml

jira:
  webhook:
    secret: auto-generated-config
  oauth:
    client_id: s2tkGiqj5TS1SOBlDP9Mc3e8m15w07pL
    client_secret: wQcADRX_rw_6VmuFBOYPi6H9Q_Lh2fNsqTu520cX5IdqoUETH1zStFItmkDtEJtA
    redirect_uri: https://f6bd-82-129-52-204.ngrok.io/jira/oauth

You can leave the oauth section blank if you are not planning to use those capabilities.

The redirect_uri value must be the public path to /jira/oauth on the webhooks path. E.g. if your load balancer points https://example.com/hookshot to the bridge's webhooks port, you should use the path https://example.com/hookshot/oauth. This value MUST exactly match the Callback URL on the JIRA integration page page.

Next steps

If you have followed these steps correctly, JIRA should now be configured with hookshot 🥳.

You can now follow the guide on authenticating with JIRA.