Fix a tracker webhook that isn't working
A tracker tells Jaah about an issue through a webhook. When the webhook is gone, switched off or sends to an old address, no issue starts a task. A tracker connection's page checks its webhooks live and says what to fix.
Who can do this: Owners and Admins of your organization. Nobody else sees Issue trackers. Fixing the webhook itself needs a Jira site admin, or a project administrator in Backlog.
Read the state of the webhook
- In the sidebar, select Settings, then Integrations, then Issue trackers.
- Select the connection's name. Its page opens on the Connection tab.
- Find the Webhook section, below the connection's fields. Last event says how long ago the tracker last sent an event, or None yet. Hover it for the time.
- Wait while State reads Checking…. Jaah is asking the tracker for its webhooks, which takes a few seconds.
- Read the row for each Jira site, or each mapped Backlog project. Its chip says the state, and a line beside it says what to do. The table below explains each state.
- Fix the webhook in the tracker, as the row says.
- Reload the page. The row should read Working.
If the section reads Could not check the webhook, Jaah could not reach the tracker. Reload the page to check again.
A Linear connection, or a Jira connection through Jaah's Jira app, has no rows to fix: the app keeps the webhook. Its State reads Working when an event arrived in the last 7 days, otherwise Managed by the app.
What each state means
| State | What it means | What to do |
|---|---|---|
| Working | The webhook sends to this connection. | Nothing. If issues still start no tasks, see Check what a tracker did with an issue. |
| Old address | Jaah's webhook there sends to another connection's address. | If that connection is gone, give the webhook this connection's address. In Jira, make a new URL and secret first: see Replace a Jira webhook URL and secret. In Backlog, paste the address the row shows. |
| Off | Jira only. The webhook exists but is switched off in Jira. | Turn it on in Jira. |
| Missing | No webhook sends to this connection. | In Jira, make a new URL and secret, then add a webhook with them under System › WebHooks. In Backlog, add a webhook with the address the row shows, under Project settings › Webhooks. |
| Unknown | Jaah can't read the tracker's webhooks. Usually the tracker account Jaah signs in with isn't an admin there: a Jira admin for a site, a project administrator for a Backlog project. | Check the webhook by hand in the tracker, or make that account an admin there. If the line says the tracker was slow, reload the page. |
Copy the Backlog address
A Backlog row that isn't Working shows the address its webhook must send to.
- Select Copy address under the row.
- In Backlog, open the project's Project settings › Webhooks.
- Paste the address into Jaah's webhook, or add a new webhook with it.
- Save the webhook in Backlog.
- Back in Jaah, reload the connection's page and check the row reads Working.
Related
- Check what a tracker did with an issue: read the events that did arrive, and why no task started.
- Replace a Jira webhook URL and secret: make a new pair for a Jira webhook.
- Start tasks from Jira: the first Jira setup and its troubleshooting.
- Start tasks from Backlog: the Backlog setup, and what to check when nothing happens.
- Issue trackers: every field on the Connection tab.