Tracker connections
Tracker connections start tasks from Linear, Jira or Backlog: an issue assigned to Jaah, a comment mentioning Jaah, or the start label files one task in the Jaah project its team or project is mapped to. Each connection owns an event automation, so its starts show under Automations.
List tracker connections
Lists the organization's tracker connections, oldest first, each with its settings and the automation its starts run under; never a secret. `jira_forge` says whether this install has Jaah's Jira Forge app. Requires the Org Owner or Org Admin role.
Create tracker connection
Connects a tracker and creates its event automation, which files tasks into the mapped projects. Returns the connection, the address the tracker posts events to and, only this once, its webhook secret or Forge claim code. Requires the Org Owner or Org Admin role; another organization's credential returns 404.
Delete tracker connection
Deletes a tracker: the connection and its automation are deleted, and the tasks it started stay. Requires the Org Owner or Org Admin role.
Get tracker connection
Returns one tracker connection with its settings; never a secret. Requires the Org Owner or Org Admin role.
Update tracker connection
Saves a connection's settings: which tracker team or project maps to which Jaah project, the start label, the done state, whether tracker users with no matching member may start tasks, and whether moving an issue to the done state completes its tasks. The automation's target follows the mapped projects. Requires the Org Owner or Org Admin role.
List tracker containers
Lists the tracker's teams, projects or spaces a mapping may name, as the tracker reports them now. Requires the Org Owner or Org Admin role.
List tracker events
Lists the connection's 50 newest events, newest first (the first is when it last received one), with what each came to: a filed task, a comment on the issue's running task, a stop, the tasks completed when the issue moved to the done state, or why nothing happened. Requires the Org Owner or Org Admin role.
Rotate tracker webhook secret
Replaces the webhook URL and secret of a connection the tracker posts to by its own address (a Jira connection whose webhook a site admin added) and returns both, only this once; the old ones stop working at once. A connection with no such webhook (Linear, Backlog, a Jira Forge app) returns 409. Requires the Org Owner or Org Admin role.
Check tracker webhooks
Reads the tracker's webhooks live: for a Jira connection whose webhook a site admin added, whether a site webhook posts to its current address, for Backlog the same per mapped project with the address to paste when it does not. Each check's state is ok, stale (a webhook posts to an old address), off, missing or unknown (the tracker would not list its webhooks). Requires the Org Owner or Org Admin role.