Jira
1. Create Atlassian OAuth app
Section titled “1. Create Atlassian OAuth app”developer.atlassian.com → Console → Create → OAuth 2.0 integration.
Scopes:
read:jira-workwrite:jira-workmanage:jira-project(if creating projects)
Callback: https://tappass.example.com/api/connect/jira/callback
2. Configure on TapPass server
Section titled “2. Configure on TapPass server”JIRA_OAUTH_CLIENT_ID=<id>JIRA_OAUTH_CLIENT_SECRET=<secret>3. Authorise
Section titled “3. Authorise”Open GET /api/connect/jira (or use the dashboard) to start the OAuth flow. TapPass stores the credential in the vault.
Operations
Section titled “Operations”| Operation | Op group | Endpoint |
|---|---|---|
search_issues |
read | GET /rest/api/3/search |
get_issue |
read | GET /rest/api/3/issue/{key} |
create_issue |
write | POST /rest/api/3/issue |
update_issue |
write | PUT /rest/api/3/issue/{key} |
transition_issue |
write | POST /rest/api/3/issue/{key}/transitions |
add_comment |
write | POST /rest/api/3/issue/{key}/comment |
list_projects |
read | GET /rest/api/3/project |
Your agent never calls Jira directly. When the model requests a Jira operation as a tool call through the governed gateway, TapPass resolves the provider, fetches the connected credential from the vault, executes the operation, and audits the call. Write operations (create_issue, update_issue, transition_issue, add_comment) are gated by your tool-decision policy.
Atlassian data residency
Section titled “Atlassian data residency”Jira Cloud supports EU region pinning — set it under Organization → Data residency in Atlassian admin. TapPass honours the resulting endpoint automatically.