Skip to main content
You will need an Atlassian account with access to the Atlassian Developer Console to create and manage OAuth 2.0 integrations.

​
Create an OAuth 2.0 integration

Register a new OAuth 2.0 integration in the Atlassian Developer Console.

1

Sign in to Atlassian

Sign in to the Atlassian Developer Console with your Atlassian account.

2

Create a new app

On the My apps page, click Create in the top-right corner and select OAuth 2.0 integration.

3

Fill in the integration details

On the Create a new OAuth 2.0 (3LO) integration screen, fill in the required fields.

  • Enter a Name (e.g., “StackOne JSM Integration”).
  • Select an Access type — Resource-level restricts access to the specific site the user selects during authorization; Account-level grants access to all resources within the customer’s account. Either type works with StackOne.
  • Check I agree to be bound by Atlassian’s developer terms.
  • Click Create.

​
Add the callback URL

Register the StackOne callback URL so Atlassian can redirect users back after authorization.

1

Open Authorization settings

In the left sidebar, click Authorization, then click Add next to OAuth 2.0 (3LO).

2

Enter the callback URL

In the Callback URLs field, enter the StackOne callback URL, then click Save changes.

  • Callback URL to enter: https://api.stackone.com/connect/oauth2/jiraservicemanagement/callback

​
Set permissions

Both Jira platform and Jira Service Management scopes are configured under the single Jira API entry on the Permissions page. By default StackOne requests every scope listed below during authorization, so enable them all — Atlassian rejects the connection if any requested scope is missing from the app. If you want to grant fewer scopes, enter the reduced list in the OAuth Scopes field in the StackOne Connector profile so only those are requested.

1

Add the Jira API

Click Permissions in the left sidebar, then click Add next to Jira API. Once added, the button changes to Configure — click it to open the scope configuration.

2

Add Jira platform classic scopes

On the Classic scopes tab, click Edit Scopes next to Jira platform REST API, enable the following required scopes, then click Save.

  • Required: Select View Jira issue data (read:jira-work) — needed for queue issues
  • Required: Select View user profiles (read:jira-user)
3

Add Jira Service Management classic scopes

Enables actions: Add Customers To Service Desk, Add Organization To Service Desk, Add Request Participants, Add Users To Organization, Create Customer, Create Organization, Create Request, Create Request Comment, Delete Organization, Delete Request Feedback, Get Organization, Get Request, Get Request Comment, Get Request Feedback, Get Request Status, Get Request Type, Get Request Type Fields, Get Service Desk, List All Organizations (Global), List All Request Types (Global), List Customer Requests, List Organization Users, List Organizations For Service Desk, List Request Approvals, List Request Comments, List Request Participants, List Request Transitions, List Request Type Groups, List Request Types For Service Desk, List Service Desk Customers, List Service Desks, Post Request Feedback, Remove Organization From Service Desk, Remove Request Participants, Remove Users From Organization

Still on the Classic scopes tab, click Edit Scopes next to Jira Service Management API, enable the following required scopes, then click Save.

  • Required: Select View Jira Service Management request data (read:servicedesk-request)
  • Required: Select Create and manage Jira Service Management requests (write:servicedesk-request)
  • Required: Select Manage Jira Service Management customers and organizations (manage:servicedesk-customer)
4

Add Jira Service Management granular scopes

Enables actions: Get Queue, Get SLA Metric By ID, List All SLA Metrics, List Queue Issues, List Queues, Perform Request Transition

Switch to the Granular scopes tab and click Edit Scopes. Use the Search by name or code box to find each scope, enable the following required scopes, then click Save.

  • Required: Select View queues (read:queue:jira-service-management)
  • Required: Select View request SLAs (read:request.sla:jira-service-management)
  • Required: Select Execute request transitions (write:request.status:jira-service-management)

​
Copy client credentials

Copy the credentials StackOne needs to connect.

1

Copy the Client ID and Secret

Click Settings in the left sidebar and scroll to Authentication details.

  • Copy the Client ID value and paste it into the Client ID field in the StackOne Connector profile.
  • Copy the Secret value and paste it into the Client Secret field in the StackOne Connector profile.
  • Treat the Secret like a password — it is shown only in this Settings page and grants access on behalf of your app, so store it securely.
  • The OAuth Scopes field in the StackOne Connector profile is optional — leave it empty to use the default scopes listed above, or enter a space-separated subset.

​
Creating the StackOne Connector Profile

To create the Connector Profile in StackOne for Jira Service Management:
1

Navigate to Connector Profiles

Login to StackOne and navigate to Connector Profiles
2

Create New Connector Profile

  • Click + Connector Profile
  • Search for and select Jira Service Management
  • Select Type as OAuth 2.0
  • Fill out the fields using details retrieved from your provider:
    • Client ID
    • Client Secret
    • OAuth Scopes (Optional)
  • (Optional) Select Actions to be enabled for this Connector Profile
  • Click Create profile
Congratulations! The new Connector Profile will now show up in your project ready to be used. You can now continue to Link Accounts for Jira Service Management.