In this article


  1. Use case #1: Epics, tasks, subtasks from a single Jira project → single airfocus project with self relations

    • When a user wants to sync the relations between epics, tasks and subtasks from a single Jira project to a single airfocus workspace.

    On Jira:

    • A user has a single project that uses Epics, Tasks and Sub-Tasks.

    On airfocus:

    • The user has a single workspace.

    • The 'Allow hierarchy relations within this workspace' within the Hierarchy tab in the workspace settings is active.

    • The user has three Jira integrations pointing to the same Jira project, but different JQL for Epics, Tasks, Subtasks.

    • Hierarchy enabled for all three integrations.

    How it looks like in airfocus once the hierarchy sync is enabled:


  2. Use case #2: Epics, tasks, subtasks from a single Jira project → multiple airfocus projects with self relations

    When a user wants to sync the relations between Epics, Tasks and Subtasks from a single Jira project to a multiple airfocus workspaces.

    On Jira:

    • A user has a single project that uses Epics, Tasks and Sub-Tasks.

    On airfocus:

    • The three airfocus workspaces already has hierarchy enabled between them.

    • Each of the airfocus workspace is integrated with the same Jira project.

    • The Jira hierarchy syncing is enabled for all integrations.

    How it looks like in airfocus once the hierarchy sync is enabled:


  3. Use case #3: Multiple Jira projects (or servers) with Epics, Tasks, etc. each → airfocus workspaces per issue type

    On Jira:

    • There are multiple projects.

    • There are multiple cloud instances / servers / combinations.

    On airfocus:

    • There is one integration per project+issue type combination.

Did this answer your question?