> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira Cloud

> Issue tracking — users & access

<Tabs>
  <Tab title="Overview">
    Connect Jira Cloud with your Atlassian email and an API token to sync site users and run access reviews. Read-only; the token is held by Nango.

    <Info>
      **Read-only access.** DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
    </Info>

    <Note>
      DSALTA collects this integration's data when you connect it — you can refresh it at any time with **Sync from integrations** on the **Integrations** page. The compliance checks below re-run once a day at 02:00 America/New\_York.
    </Note>

    ## What DSALTA reads

    DSALTA reads the Jira Cloud user roster — names, emails and active status, which appears on your **Access** page; and your Jira Cloud resources, which appear on your **Inventory** page. Jira's user-search API exposes no per-user role or permission scheme, so every account is listed as a Member, and the roster is a filtered subset: only Atlassian-type accounts are kept, while app/bot accounts (Connect apps and service accounts), Jira Service Management customer accounts and guests are dropped before the sync — so DSALTA's user count is lower than the total on Jira's own user-management screen. Deactivated accounts are kept and shown as Inactive.

    It calls these Jira Cloud endpoints:

    * `/rest/api/3/myself`
    * `/rest/api/3/users/search`
    * `/rest/api/3/project/search`

    Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Jira Cloud environment.

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="How do I check whether the connection is healthy?">
        Open **Integrations** in the DSALTA sidebar, stay on the **Connected** tab, and click **Manage** on the integration's card. Open the **Status** tab: it shows either **Connected and working properly** or **Connection issues detected**.

        Use the **Status** tab, not **Overview** — Overview always reports **Connected** regardless of the real state.
      </Accordion>

      <Accordion title="A check shows Failed and nothing changed on my side">
        On an integration-powered check, **Failed** normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to **Source Data**, and read the result code: **403** is a missing permission, **428** is a setting DSALTA still needs, **500** is a failure on DSALTA's side.

        A real compliance gap shows **207** and leaves the test looking **Completed**. See [Understanding Test Results](/guides/data-library/test-results).
      </Accordion>

      <Accordion title="Data looks out of date">
        Compliance checks re-run once a day at 02:00 America/New\_York. To refresh sooner, open **Integrations → Connected** and click **Sync from integrations** at the top right — it refreshes every connected integration at once.
      </Accordion>

      <Accordion title="How do I repair a broken connection?">
        There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.

        <Warning>
          **Disconnecting is destructive and cannot be undone.** DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see [Integration errors](/troubleshooting/integration-errors).
        </Warning>
      </Accordion>

      <Accordion title="Configure scope will not let me change anything">
        That is expected. **Configure scope** is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="How to connect">
    **Before you begin**

    * The Atlassian account whose token you use needs the **Browse users and groups** global permission in Jira. It is granted by default on most sites, but without it the user search endpoint is refused and DSALTA's Access page comes back empty even though the connection validates successfully.

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **Jira Cloud**, and click **Connect** to open the connect panel.
      </Step>

      <Step title="Create an Atlassian API token">
        Go to [id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens), click Create API token, give it a label (e.g. DSALTA), then copy the token — it's shown only once.

        <Tip>Use the **Create API token** button, not **Create API token with scopes**. DSALTA connects over Basic auth and requests no scopes at all, so a scoped token will be rejected by the Jira REST calls it makes.</Tip>

        <Tip>Atlassian API tokens expire — you choose an expiry between 1 and 365 days, and the default is one year. Note the expiry date somewhere you will see it: when the token lapses, Jira stops syncing, and because DSALTA has no Reconnect button you have to Disconnect and connect again, which permanently deletes the data and tests already collected from Jira.</Tip>

        <Tip>Atlassian warns that "New tokens may take up to a minute to work after they've been created." If the connection is rejected immediately after you paste a brand-new token, wait a minute and try again before assuming it is wrong. You can also hold at most 25 tokens per account at a time.</Tip>

        <img src="https://mintcdn.com/dsalta/4UzgskHSsjeDN5e5/images/integrations/jira/01-atlassian-api-tokens.png?fit=max&auto=format&n=4UzgskHSsjeDN5e5&q=85&s=d6e5d8c77820a7334c585b142e96b48a" alt="Atlassian Account Security page showing the API Tokens screen with Create API token, Create API token with scopes and Revoke all API tokens buttons above a list of existing tokens" style={{maxWidth:"720px",width:"100%",borderRadius:"8px"}} width="2704" height="906" data-path="images/integrations/jira/01-atlassian-api-tokens.png" />
      </Step>

      <Step title="Find your Jira site domain">
        Look at your Jira URL: [https://your-domain.atlassian.net](https://your-domain.atlassian.net). The part before .atlassian.net (e.g. your-domain) is your site domain — you'll enter just that part, not the full URL.

        <img src="https://mintcdn.com/dsalta/4UzgskHSsjeDN5e5/images/integrations/jira/02-jira-site-domain-url.png?fit=max&auto=format&n=4UzgskHSsjeDN5e5&q=85&s=a7e718b1bb2c7d3387a7a84ea7166d97" alt="Jira Cloud in a browser with the address bar showing karanahuja322.atlassian.net, alongside the Spaces list" style={{maxWidth:"720px",width:"100%",borderRadius:"8px"}} width="2930" height="1522" data-path="images/integrations/jira/02-jira-site-domain-url.png" />
      </Step>

      <Step title="Connect">
        Enter your Atlassian account email as the username, the API token you copied as the password, and your site domain from the previous step.

        The username must be the email address of the Atlassian account that created the token. A token is bound to the account that generated it, so an email belonging to a different Atlassian account will be rejected even when that account has access to the same site.
      </Step>
    </Steps>

    <Check>
      Once connected, Jira Cloud appears on the **Connected** tab and the checks below begin reporting after the first sync.
    </Check>
  </Tab>

  <Tab title="Automated checks">
    Each check below re-runs once a day, at 02:00 America/New\_York, while this integration is connected. Click any check for step-by-step remediation guidance.

    | Check                                                                                                               | Severity | What it verifies                                                                |
    | ------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------------------------------------------------------- |
    | [User access to Critical System should be valid](/integrations/jira/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with Jira access is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/jira/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active Jira access.             |
  </Tab>

  <Tab title="Useful links">
    | Topic   | Link                                                                                                                                               |
    | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
    | Setup   | [Manage API tokens for your Atlassian account](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/) |
    | General | [Jira Cloud website](https://atlassian.com)                                                                                                        |
    | DSALTA  | [Connection error messages](/troubleshooting/connection-error-messages)                                                                            |
  </Tab>
</Tabs>