What rkito uses Jira for
| Feature | Mechanism |
|---|---|
| Import Jira issue as CHI | OAuth 2.0 (3LO) — reads issues from connected site |
| Bi-directional status sync | Posts status updates back to Jira via API |
| Webhook callbacks | Jira pushes issue events to rkito (inbound) |
Important: Atlassian OAuth 2.0 rejects localhost redirect URIs. A publicly reachable HTTPS URL is required — use your production domain or a tunnel for testing.
1. Create the Atlassian app
1
Go to the Atlassian Developer Console at developer.atlassian.com/console/myapps/
2
Click Create → OAuth 2.0 integration
3
Name it rkito
2. Configure OAuth 2.0 (3LO)
1
In your app, click Authorization in the sidebar
2
Under OAuth 2.0 (3LO), click Add
3
Set the Callback URL:
| Environment | Callback URL |
|---|---|
| Production | https://api.yourdomain.com/api/v1/integrations/jiras/installations/callback |
3. Configure API scopes
Click Permissions in the sidebar and add these Jira API scopes:
| Scope | Why |
|---|---|
| read:jira-user | Read user profile of the authenticated user |
| read:jira-work | Read issues, projects, boards |
| write:jira-work | Post comments, update issue status |
| offline_access | Issue a refresh token for long-lived access |
4. Set environment variables
# api/.env JIRA_CLIENT_ID=<Client ID from Atlassian console> JIRA_CLIENT_SECRET=<Secret from Atlassian console> JIRA_REDIRECT_URI=https://api.yourdomain.com/api/v1/integrations/jiras/installations/callback # Where to redirect after successful OAuth APP_URL=https://app.yourdomain.com
5. Set up inbound webhooks (optional)
Enables automatic CHI status updates when Jira issues change state.
1
In Jira, go to Settings → System → WebHooks (requires Jira admin)
2
Click Create a WebHook
3
Configure URL: https://api.yourdomain.com/api/v1/integrations/jiras/webhook
4
Subscribe to events: Issue created, Issue updated, Issue deleted
5
Add the webhook secret to api/.env as JIRA_WEBHOOK_SECRET
6. Connect from rkito
1
In rkito, navigate to your org → Integrations → Jira
2
Click + Connect → Connect Jira
3
A new window opens to Atlassian — log in and authorise rkito
4
You are redirected back to /integrations/jiras — the new integration appears in the table
Common errors
invalid_redirect_uri
The JIRA_REDIRECT_URI env var must be character-for-character identical to what is registered in the Atlassian Developer Console — no trailing slash, no http/https mismatch.
Callback URL rejected by Atlassian
Atlassian requires HTTPS and a publicly reachable host. localhost and http:// URLs are rejected.
User redirected to localhost after OAuth
APP_URL in api/.env is still pointing at localhost. Update it to your BUI domain and restart the API.