In this article

Benefits of using the Jira integration

Connect your product management workflows, prioritization frameworks, and roadmaps with day-to-day development by syncing your data seamlessly between airfocus and Jira.

The integration is compatible with Jira Cloud, Jira Server, and Jira Data Center.

  • Import Jira issues (as items) into airfocus.

  • Push airfocus items into Jira (as any issue type).

  • Two-way sync & flexible filtering (custom JQL).

  • Flexible field mapping.

  • Display your airfocus priority scores in Jira for context around business value and priorities.

  • Ability to see the parent-child relationships directly in airfocus (beta).

The initial setup of a new Jira integration

First, sign up for airfocus or log into your existing account. Create a new workspace in airfocus or select the one you would like to integrate Jira with.

Note that you have to authorize your Jira instance only once per airfocus team.

Our Jira integration is compatible with Jira Cloud, Jira Server, and Jira Data Center.

You can add multiple Jira integrations to a given workspace (e.g. from different Jira projects or instances).

To do that, simply go to the Extensions section within your workspace, click on "Add integrations" and Connect with Jira.

Untitled.jpeg (1135×1052)

Select "Connect to a new Jira instance", enter your Jira instance URL (e.g. and click on "Proceed".

Follow the directions of the Authorization Wizard ****to authorize the application linking between Jira and airfocus.

Configure integration filtering

The first step is to add a name for your integration. It might make sense to name your integration after the Jira project that you’ll integrate with. This is especially helpful if you connect multiple Jira projects with one of your airfocus workspaces.

This will make it easy to understand where different items are coming from. You could then easily use a filter to only show items from a Jira project.

Decide which Jira project and issue types you want to import or sync. For issue types, use JQL to specify criteria for which issues to load (read more about JQL here).

Example: If you just want to import/sync Jira epics and stories with a “To Do” status, simply use this command: issuetype in (Epic, Story) AND status = "To Do"

How does the airfocus <> Jira field mapping work?

Use mapping to define how information in Jira should be mapped to information in airfocus. If you change an issue or item in one system, the other system will be adjusted accordingly.

You can, for example, define how Jira statuses should be mapped to airfocus single-select fields and/or how Jira labels should be mapped to airfocus multi-select fields.

There are also many more options to map different Jira custom and system fields to your airfocus fields.

How to map fields

When you take a look at the field mapping options, you'll see that two fields are always mapped by default: The item names and item descriptions.

You can define for each of your fields whether you want to have a one-way synchronization or a two-way synchronization between the field in Jira and airfocus.

You can set the mapping directions for all fields at once (as far as technically possible) with the “Set direction” button.

By default, the mapping direction is set from Jira to airfocus only and can be changed by the user to whatever is available for mapping.

When setting up a new mapping for one of your fields you’ll find that you’re only able to map Jira field to airfocus fields if both ends have the same field type.

When selecting a field in the dropdown, only fields that match the field type will be displayed in the dropdown on the other end.

After selecting two fields that you want to map you can select the field options and how they should be mapped:

Overview of all mappable fields types

Mappable Jira system fields:

Mappable Jira custom fields:

Configure additional settings

When "Archive unknown issues" is enabled, then previously imported items will be archived in airfocus if they are not present in Jira anymore (or just do not match the JQL filter anymore).

When "Automatic syncing" is enabled, your integration will automatically sync every 10 minutes and every time you access the workspace.

When you click "View logs", you can view your Jira integration activity logs and see what changes were made before the last sync.

Hierarchy sync

Hierarchy sync for Jira allows you to sync the parent-child relations automatically from your Jira project to airfocus (one-way for now). This allows you to do product management work on airfocus while having the latest Jira hierarchy in sight without needing to switch between airfocus and Jira. You can find the list of example use cases here.

💡 To set up/enable the Hierarchy sync for Jira (beta), you’ll need:

  • Two or more workspaces with airfocus hierarchy enabled between them OR a workspace that allows hierarchy relations within the same workspace.

  • Ensure that you sync at least 2 Jira issue types to airfocus.

    • If you have two integrations ****in two workspaces, then you should sync a single item type for each workspace.

    • If you have two integrations in one workspace, then should sync a single item type for each of the integrations in that one workspace.

  • A user would require a full access to the workspace in order to change anything in the integration.

Step #1

To start, ensure that the airfocus product hierarchy is enabled with another or within your current workspace.

Step #2:

Then, head to the Jira integration settings page, and click “Enable” to enable the Hierarchy sync for Jira.

Once the Hierarchy sync is enabled, then you’ll be able to select the workspaces/integrations to connect.

You can choose any workspace that fulfils the following:

  • The other workspace has a hierarchy relation to the current one.

  • The other workspace has Jira integration to the same Jira instance.

  • The user has full access to the other workspace.

  • The other workspace is in the same airfocus team.

Step #3

Once you have the Hierarchy sync enabled, you can see the parent-child relationships directly in airfocus.

Please note the following when enabling Hierarchy sync for Jira:

  • The integration only adds the relations between synced items, not additional items. This means that items have to be synchronized by their respective integration already before hierarchy links will be synced.

  • The Jira API does not reveal the children of an epic which means that it prevents airfocus from detecting whether a Jira epic has any children issues. In order to see the child relationships on airfocus, the epic already has to be synced to airfocus when you sync the children level issues in order for all relationships to be reflected correctly on airfocus.

  • Hierarchy sync for Jira can also be configured within the same workspace, if multiple Jira issue types are synced to the same airfocus workspace (either through a single or multiple integrations) and has enabled 'Allow hierarchy relations within this workspace' within the Hierarchy tab in the Workspace settings.

  • A user would require at least read access to the connected Jira project in order to enable Hierarchy sync for Jira.

Additional information

  • To connect another Jira project from the same Jira instance with your workspace, you don't have to go through the authentication process again. You only have to link (and authenticate) your Jira instance with your airfocus team once.

  • You can simply add another Jira project integration on the integrations page from now on. The setup will only require selecting the instance and starting the mapping right away.

  • Looking for static IP's to white-list for your Jira Server integration? Click here 👋

Related questions

Have questions? Please get in touch via chat. We reply usually within minutes.

The first modular product management platform: Discover, learn, plan and deliver - your way.

Not yet an airfocus user? Start your free trial today and join thousands of teams who use our flexible (product management) platform to build products that matter.

Start your free trial today

Did this answer your question?