Set up a Jira Cloud connector
Yes, there are TWO kinds of Jira integration! The instructions below connect a Jira Cloud instance with ConductorOne so that you can review access data and grant user access to Jira.
If you want to set up an integration with Jira Service Management that allows ConductorOne Copilot to create, modify, and resolve Jira service desk tickets, go to Generate access requests through a service desk.
Capabilities
Sync user identities from Jira Cloud to ConductorOne
Resources supported:
- Projects
- Groups
Provisioning supported:
- Group membership
Known limitations
- User Email is not currently synchronized
- Will only list the first 1,000 users of a project
Add a new Jira Cloud connector
This task requires either the Connector Administrator or Super Administrator role in ConductorOne.
In ConductorOne, click Connectors > Add connector.
Search for Jira Cloud and click Add.
Choose how to set up the new Jira Cloud connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
Do you SSO into Jira Cloud using your identity, SSO, or federation provider? If so, make sure to add the connector to the unmanaged Jira Cloud app that was created automatically when you integrated your provider with ConductorOne, rather than creating a new managed app.
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
A Jira Cloud connector owner must have the following permissions:
- Connector Administrator or Super Administrator role in ConductorOne
- Administrator access in Jira Cloud
- Click Next.
Next steps
If you are the connector owner, proceed to Configure your Jira Cloud connector for instructions on integrating Jira Cloud with ConductorOne.
If someone else is the connector owner, ConductorOne will notify them by email that their help is needed to complete the setup process.
Configure your Jira Cloud connector
A user with the Connector Administrator or Super Administrator role in ConductorOne and Administrator access in Jira Cloud must perform this task.
Step 1: Create an API token
Log into your Jira account with Administrator access.
Navigate to https://id.atlassian.com/manage-profile/security/api-tokens.
Click Create API token.
Give your token a label, such as ConductorOne, and click Create.
Carefully copy the newly generated API token. We’ll use it in Step 2.
Step 2: Add your Jira Cloud credentials to ConductorOne
In ConductorOne, navigate to the Jira Cloud connector by either:
Clicking the Set up connector link in the email you received about configuring the connector.
Navigate to Connectors > Jira Cloud (if there is more than one Jira Cloud listed, click the one with your name listed as owner and the status Not connected).
Find the Settings area of the page and click Edit.
Enter your Jira Cloud domain (the URL of your Jira Cloud instance is
<YOUR DOMAIN>.atlassian.net
) into the Jira site domain field.Enter the username for your Jira Cloud account in the Username field.
Paste the API token you generated in Step 1 into the API key field.
Optional. If you want to automatically create Jira Cloud tickets to track provisioning tasks, click to Enable external tick processing. Read more about external ticketing system integrations here.
Click Save.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
That’s it! Your Jira Cloud connector is now pulling access data into ConductorOne.
Configure the Jira Cloud integration using Terraform
As an alternative to the integration process described above, you can use Terraform to configure the integration between Jira Cloud and ConductorOne.
See the ConductorOne Jira Cloud integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.