Jira

Atlassian's issue tracker: projects, issues, comments, boards, sprints and backlogs

Connects by
Signing in with Atlassian
Category
Projects and tasks
Part of
Atlassian
Tools
689
ServiceKey
Jirajira

Connecting

Your client presses Connect on their link and approves on Atlassian's own screen. Operate As never sees their password.

Check they're connected
curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"
Response
[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "jira"    ]  }]

Permissions

What the client readsPermission it asks for
See your projects and issuesread:jira-work
Create and change issues and commentswrite:jira-work
See the people in your Jira sitesread:jira-user
See your boardsread:board-scope:jira-software
Change your boardswrite:board-scope:jira-software
See your sprintsread:sprint:jira-software
Plan and change sprintswrite:sprint:jira-software
See issue detailsread:issue-details:jira
See your projectsread:project:jira

Tools

Install Jira's typed package for your language:

pip install operate-as-jira
Run jira.add_actor_users
curl -X POST https://api.operate.as/v1/actions/jira.add_actor_users \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "project_id_or_key": "<project_id_or_key>",      "id": "<id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/jira.add_actor_users

Response
{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://api.atlassian.com/ex/jira/{cloud_id}, with the parts in braces filled in from your client's account. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint
curl "https://api.operate.as/v1/clients/6f1c2a7e-.../jira/..." \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"
Response
{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Atlassian refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer
HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Atlassian access ended. Send them their link to reconnect."}
Your webhook receives
{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "atlassian",    "services": [      "jira"    ],    "reconnectUrl": "https://…"  }}