Capabilities
The Jira Cloud connector supports automatic account provisioning. To provision accounts, the app’s Provisioning step must include a Connector step with mappings for both required fields:
Both mappings are required. If the
products mapping is missing, the Atlassian API rejects the request with an HTTP 400 error, and the connector reports this as a generic “failed to create user” error without surfacing the upstream message, so the cause may not be immediately obvious.
This connector does not support account deprovisioning or suspending and restoring accounts. These operations apply to the Atlassian account across every Atlassian product, not just Jira, so they’re handled at the Atlassian organization level. To deprovision, suspend, or restore accounts, and to sync whether an Atlassian account is active, suspended, or deactivated, configure the Atlassian connector.
This connector can be configured to sync app accounts from the Jira API and managed accounts and managed groups from Atlassian.
This connector can also be configured to automatically create and update Jira tickets to track manual provisioning assignments. Go to Configure Jira Cloud as an external ticketing provider to learn more.
Account status
When the optional Atlassian organization settings are configured, C1 sets the status of accounts synced from your Atlassian organization from the status Atlassian reports for each user. Accounts synced from the Jira API only report whether they’re active, so they’re shown as Enabled or Disabled.
If Atlassian reports any other status, C1 marks the account Enabled only when both the account and the membership are active, Disabled when either one is inactive, closed, suspended or missing a membership, and leaves the status unspecified when it can’t tell.
Known limitations
- User email is synced only when Atlassian returns it. Depending on the account’s profile-privacy settings and the API token’s permissions, Atlassian may omit the email address, in which case the connector cannot populate it.
- Project participant listing is subject to an Atlassian API constraint: each request selects up to 1,000 candidate accounts and then filters them for browse permission, so a request returns fewer accounts than requested. Enumeration for a project stops at the first request that returns no accounts, which means a run of 1,000 or more consecutive accounts without browse permission on a project ends that project’s participant listing early.
Gather Jira Cloud credentials
Configuring the connector requires you to pass in credentials generated in Jira Cloud. Gather these credentials before you move on.Create an API token
You can set up the connector using either a classic (unscoped) or a scoped token.1
Log into your Jira account with Administrator access.
3
Click Create API token.
4
Give your token a label, such as C1, and click Create.
5
Carefully copy and save the newly generated API token.
-
Scope:
read:jira-user
Purpose: Sync users and groups. -
Scope:
read:jira-work
Purpose: Sync projects and roles; read issue data, schemas, and statuses. -
Scope:
write:jira-work
Purpose: Create tickets (required if using the connector as an external ticketing provider). -
Scope:
manage:jira-project
Purpose: Provision project role membership. -
Scope:
manage:jira-configuration
Purpose: Provision group membership.
Additional credentials
To set up the connector, you’ll also need:-
If using a classic token, your Jira Cloud URL in
https://your-domain.atlassian.netformat -
If using a scoped token, your cloud ID, which can be found at
https://<your-domain>.atlassian.net/_edge/tenant_info - The email address for your Jira Cloud account
Optional: Create an Atlassian organization API key
If you want to set up the Jira Cloud connector to sync managed accounts and managed groups from Atlassian, you’ll need to generate an Atlassian API token and look up your Atlassian organization ID.1
Log into your Atlassian account and select your organization, if relevant.
2
Navigate to Settings > API keys.
3
Click Create API key.
4
Select API key without scopes, then click Create API key.
5
Review the key info and click Create. The new organization API key is generated.
6
Carefully copy and save the API key and the organization ID.
Configure the Jira Cloud connector
- Cloud-hosted
- Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.Done. Your Jira Cloud connector is now pulling access data into C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for Jira Cloud and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
Enter your Jira Cloud domain into the Jira site domain field:
- If using a classic API token without scopes, use the format
<YOUR DOMAIN>.atlassian.net. - If using a token with scopes, use the format
https://api.atlassian.com/ex/jira/<cloud-id>.
9
Enter the email address for your Jira Cloud account in the Your Jira email address field.
10
Paste the Jira API token into the API token field.
11
Optional. Click to Enable external ticket provisioning.
12
Optional. In the Project keys field, enter a comma-separated list of Jira Cloud project keys to limit which projects are used when creating external tickets. If left empty, all projects accessible to the service account will be used.Project keys that don’t match an existing project are ignored without a warning, so check the keys for typos. After you change this field, the ticket schemas offered in C1 are updated on the next sync.
C1 shows at most 100 ticket schemas per connector. Each project adds one schema per issue type, except Epic, Bug, and sub-task types. If project or issue type options are missing, list only the projects you need in this field. Atlassian documents a maximum of 50 project keys for project filtering. Very long lists (several hundred keys) exceed the request URL length limit, and external ticket processing fails with a
414 Request URI Too Long error.13
Click Save.