> For the complete documentation index, see [llms.txt](https://documentation.ardoq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ardoq.com/integrations/out-of-the-box-integrations/jira-software-cloud.md).

# Jira Software Cloud

Learn how to set up and configure the integration between Jira Software Cloud and Ardoq.

Jira Software Cloud is a powerful tool for project management and issue tracking, widely used in software development. By integrating Jira Software Cloud with Ardoq, the combination allows for a more dynamic and actionable enterprise architecture, ensuring that IT initiatives are closely aligned with business goals and strategies.

{% hint style="info" %}
This integration is supported for Jira Software for Cloud only. We do not support the self-managed version at this time.

The importer is limited to ingesting 5000 objects per table. We recommend applying the `created >= -26w` JQL filter as a start to limit the import scope of epics, stories, and bugs to those created in the last 6 months.
{% endhint %}

## Relevant Use Cases <a href="#h_e3143089de" id="h_e3143089de"></a>

The Jira integration enhances the **Strategy to Execution Use Case** by facilitating tracking and management of initiatives critical to achieving strategic objectives. Specifically, it can import the following resources:

* Projects, Epics, Stories, Tasks, Bugs, Users, Issues
* Ideas from Jira Product Discovery
* Ticket start and end times
* URL
* Status + custom status
* Custom fields
* Reporter/assignee (email and display name)

## Connecting to Jira

You will need to create an API token to allow Ardoq to pull in data from your instance of Jira. Refer to Jira [token management documentation](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/) for more details.&#x20;

<figure><img src="https://2484004798-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnlnB7uZ29iLVLzqGbCym%2Fuploads%2FBfiOgXhSMjb8FabQipS0%2Fimage.png?alt=media&amp;token=7525bd82-90b0-44f4-b702-fbea380ae6f6" alt=""><figcaption></figcaption></figure>

## Filtering data with Jira Query Language (JQL)

You can control the resources you bring in from Jira using JQL. The **Filter** button is available in the **Select data** step for the epics, stories, tasks, bugs, ideas, and issues resources.

<figure><img src="https://2484004798-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnlnB7uZ29iLVLzqGbCym%2Fuploads%2FCFKr8Za6qAzHvTM5k6Gb%2Fimage.png?alt=media&amp;token=1951e9eb-c2f1-44b6-aadf-920efbc4a025" alt=""><figcaption></figcaption></figure>

For example, to fetch a specific set of projects that aren't closed you can use a query like the following:

```
project in (Project1, Project2, ProjectN) AND status != CLOSED
```

Each query applies to each table independently — if you have many resources of different types, you will need to apply JQL filters on every resource you want to import.