Jira & issue trackers

Jira (OAuth)

A team admin connects Jira from Dashboard → Integrations → connect Jira. It's a standard Atlassian OAuth 2.0 (3LO) flow: you authorize stndp against a Jira site, and the resulting tokens are stored encrypted. stndp then tracks that site's projects and work items.

From the terminal:

stn projects                 # tracker projects you can see (provider shown per row)
stn project PROJECT_ID       # one project: its work items and the repos that track it
stn search "PROJ-123"        # find a ticket by key, with its connected work
stn link 7 PROJ-123          # attach a Jira ticket to an entry / checkpoint / decision

Where a repo's commits reference a project's tickets, stndp records a repo↔project mapping with a confidence level, visible in stn repo.

Linear, ClickUp & Monday

The platform's data model tracks work items from Linear, ClickUp, and Monday as well — they appear in stn projects, stn search, and the graph the same way Jira items do. Today these surface by linking and via inbound webhooks rather than a one-click OAuth button (that's currently Jira, plus GitHub and Slack):

stn link 7 https://your-org.atlassian.net/browse/PROJ-123
stn link 7 ENG-456            # any tracker key or url

A linked ticket carries its provider and external id into the graph, so it shows up alongside the entry, checkpoint, or decision it belongs to.