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.
This integration is supported for Jira Software for Cloud only. We do not support the self-managed version at this time.
We suggest to limit the import to less than 5000 objects. If you want to import more, please contact our in-app support.
Relevant Use Cases
Ardoq's new Jira Software Cloud integration enhances the Strategy to Execution Use Case by facilitating seamless tracking and management of initiatives critical to achieving strategic objectives. It allows for the importation of projects, epics, and tasks directly from Jira, ensuring that execution tasks are accurately represented and connected to strategic objectives within Ardoq. This integration streamlines the alignment of initiatives with business goals, enables efficient monitoring of progress, and supports the agile reprioritisation of tasks in response to changing business conditions.
Key Features of the Jira Software Cloud Integration
Ability to import
Projects, Epics, Stories, Tasks, Bugs
Ticket start, end (date-time)
URL
Status + custom status
Custom fields
JQL query for advanced search
Reporter/assignee (email and display name)
Daily/weekly automatic synchronisations
At this time we don't support exporting into Jira or pulling data from Jira into Ardoq more than once a day.
Setting up Jira Software Cloud
In the Ardoq platform, go to Import & integrations and click Jira Software Cloud.
On the homepage of the integration, you can navigate to your scheduled syncs you set up when you've done an in import, list of your specific configurations, and connections that have been set up.
To get started, connect your Jira account to Ardoq under the connections tab. To connect the integration to your organization's Jira Software account, you need to provide the below information:
Connection name: Any name you'd like to call the connection. You'll use this connection when you move to importing Jira data.
Base URL: Check your browser URL when logged into your organization's Jira instance.
Note 1: Don't paste the full URL, only the identifier in the URL for your domain
Note 2: If you don't have an atlassian.net URL, then use the custom domain field
Jira Software Email: Your email associated with the Jira account.
Jira Software API Token: Generate an API Token. Please read more here.
Select Data
Select Connection
Select the connection you created in the previous step.
Select tables and fields
Choose which tables and fields you want to import to Ardoq. If you have any custom fields, these will show.
Optional — JQL (Jira Query Language) query
On this step of the import you can optionally run a JQL (Jira Query Language) query for Epics, Stories, Tasks, Bugs and Issues.
Note: This is not possible for Users or Projects. Running JQL queries in Jira enables precise filtering and quick access to specific issues.
An example of a JQL query
To fetch a specific set of projects that aren't closed:
project in (Project1, Project2, ProjectN) AND status != CLOSED
Configure Data
Similar to other Ardoq integrations, map the table data and configure the columns. Choose what workspace you want the data to be imported to. Below Table details you can see what specific types of objects will be added to the workspace you have selected and if there are any warnings or errors preventing you from completing the import process.
Review Import
Upon opening the workspace you have created with the imported objects, you can set scheduled import. You have the opportunity to choose schedule sync on a daily or weekly basis. Any new objects that fall into the import you have run will automatically be added to the workspace.
