Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 04:45 UTC
How do I set up custom OAuth credentials for Jira?
Use your own Atlassian OAuth 2.0 (3LO) app when you want the consent screen to show your app name and to control which scopes it can grant.
Create the Atlassian app
- Sign in to the Atlassian developer console (create a developer account if you don't have one).
- Click Create → OAuth 2.0 integration, name the app, and click Create.

- Open Authorization in the sidebar and click Configure next to OAuth 2.0 (3LO). Set Callback URL to
https://backend.composio.dev/api/v1/auth-apps/addand click Save changes. It must exactly match the auth config'soauth_redirect_urifield.

- Open Permissions. Click Add next to the Jira API, then Configure, and add every classic or granular scope your auth config will request (see below). Add the User Identity API too if you need user profile scopes. Click Save.


- Open Distribution and set the status to Sharing if users outside your own Atlassian account will connect. Atlassian asks for a vendor name, privacy policy URL, and a personal data declaration.
- Open Settings and copy the Client ID and Secret under Authentication details.
Create the auth config in Composio
- In the Composio dashboard, go to Auth Configs → Create and select Jira.
Choose OAuth 2.0 and Your Own Credentials, then paste the Client ID and Secret.
Remove any scopes you didn't add on the app's Permissions tab, then click Create Auth Config.
Click Connect Account and enter your site's subdomain: the part before
.atlassian.netin your browser's address bar. Forhttps://acme.atlassian.net, enteracme.Approve the consent screen and check that the account shows Active.
See custom auth configs for the general flow.
Scopes
The default auth config requests the classic scopes read:jira-work, write:jira-work, read:jira-user, manage:jira-project, manage:jira-configuration, manage:jira-webhook, and manage:jira-data-provider; Jira Service Management scopes (read:servicedesk-request, write:servicedesk-request, manage:servicedesk-customer, read:servicemanagement-insight-objects); Jira Software granular scopes for sprints and boards; read:project:jira and read:issue-type-scheme:jira; and offline_access. The service management scopes live under the Jira Service Management API on the Permissions tab, so add that API too or remove those scopes from the auth config. See Atlassian's Jira scopes reference.
Every scope the auth config requests, apart from offline_access, must also be added on the app's Permissions tab. If one is missing, the connection fails with a "Something went wrong" error. Keep offline_access in the auth config's scopes: Atlassian only issues a refresh token when it's requested, and without one the connection stops working when the access token expires.

What is the difference between JQL GET, JQL POST, and Search Issues?
JQL GET and POST target the same search functionality but use different HTTP methods. POST supports complex queries in the request body. Search Issues uses JQL POST under the hood with extra parameters and filters. For consistent results, prefer POST for complex queries. Use the fields parameter to request specific fields, or ["*all"] to request all fields.