Skip to main content
Jira integration is two steps: connect once per user, then link a specific Jira project to each Hideout project. Once linked, mention Jira issues directly in the New Agent chat.
Where: Platform → Profile → Integrations for the account connection, then Project Settings → Integrations to link a project.

​
1. Connect Jira (account-level)

Profile → Integrations → Connect Jira. You’ll be sent to Atlassian to authorize the workspace, then dropped back on Project Settings with a “Connected” badge. Permissions requested: read:jira-work, read:jira-user, and offline_access (so the connection refreshes itself). On Project Settings → Integrations, the Jira card now shows every Jira project visible to your account. Pick the one this Hideout project should mirror.

​
What you get

In the New Agent chat, type a Jira identifier (e.g. KAN-42) anywhere in your message. Seb pulls in the issue’s title and description as context and tags the launch with it. Tickets resolve on demand at agent-launch time, against live Jira.

​
Disconnecting

Profile → Integrations → Jira → Disconnect clears tokens. Projects you own that linked to a Jira project lose the link; teammates’ links survive until they disconnect themselves.

​
Troubleshooting

  • “Jira connection expired” — token was revoked or refresh failed. Reconnect from Profile.
  • Project picker is empty — your Jira account doesn’t have access to any projects. Check Atlassian permissions.
  • “Couldn’t find ticket KAN-42” — the identifier doesn’t exist in the linked Jira project, or your account doesn’t have permission to see it. Check the project link on Project Settings → Integrations.