Updating PSA Project Structure to Show Jira Hierarchy

Once you have enabled PSA Direct for Jira, depending on your configuration, you can use it to:

Note:

Before you update PSA projects to show the Jira hierarchy, you must ensure that PSA users have set up correct authentication access to the Jira server. If PSA users fail to set up correct authentication, the connector will not update PSA projects to show Jira hierarchy and send an email notification.

The Jira Parent Task field holds the PSA task that is synchronized with the Jira parent issue. For more information, see Project Task Fields.

Using the Jira Parent Task field means that your hierarchy in PSA does not need to be the same as your Jira hierarchy.

The Jira Parent Task field is populated automatically when the Jira issue is synced to the PSA task, but you can set it manually before syncing to reflect different relationships. You can only link one Jira Issue with one PSA Task.

Note:

If the PSA Project Task has already been synced with Jira, then you cannot update the Jira Parent Task field. To do so, you must use the Move option in Jira to change the Jira Parent Task.

PSA Project structures are automatically updated in PSA to show Jira Project hierarchy if you have enabled the following in the PSA Direct for Jira Settings tab:

  • Sync PSA Projects to Jira
  • PSA projects to be mapped to Jira projects
  • Sync Jira Issues to PSA Project Tasks
Note:

PSA Direct for Jira only updates the Jira hierarchy for the Jira Issue Type listed in the Jira Issue Type Settings. The name of the Jira Issue Type is case-sensitive and must be followed in the same way. Otherwise, PSA Direct for Jira fails the synchronization.

Before you start updating the PSA Project structure to show the Jira Project hierarchy, ensure that you have enabled the Jira Parent Task field to be reflected in the PSA Project Task object via Upgrade PSA Direct for Jira feature in Feature Console. If you fail to do that, PSA Direct for Jira fails to update the PSA Project structure to show the Jira Project hierarchy.

The example below assumes that an Epic is the highest issue type in your Jira project hierarchy.

To update PSA Project structure to show Jira Project hierarchy:

  1. In a Jira project that is synced with a PSA project, create an Epic as Issue Type in Jira. For this example, we are synchronizing with a Jira project with the key NORTH. Enter Planning under the Summary field.
  2. [Optional] Enter the description of the Epic.
  3. Enter an Epic name to identify the Epic. For example, enter Planning.
  4. Click Create.

    The connector automatically creates the Planning in the PSA Project Task. Once the synchronization finishes, the Correlation ID field populates with the ID of the Epic in Jira. For example, NORTH-8.

    Note:
    • In this case, the Jira Parent Task Link is not populated because the Jira Epic is at the top of the hierarchy.
    • In the Jira Issue Type field, the type is populated depending on the selection of the Issue Type field in Jira. For example, in this case, it is Epic.
    • In the Jira Issue Type Category field, the category is populated depending on the selection in Jira. For example, in this case, it is Standard Issue Type.
  5. In Jira, create a Jira Task under the Epic.
    1. Select Issue Type to Task and enter summary. For example, Scope writing.
    2. [Optional] Enter the description of the Task.
    3. By default, the Epic Link is populated with Planning.
    4. Click Create.

      The connector automatically creates the Scope writing in the PSA Project Task. Once the synchronization finishes, the Correlation ID field populates with the ID of the Task under Epic in Jira. For example, NORTH-9.

      • In the Jira Parent Task field, the link to a PSA Project Task is populated. This is the PSA Project Task that links to the parent issue in Jira. For example, in this case, the Epic is a Planning.
      • In the Jira Issue Type field, the type is populated depending on the selection of the Issue Type field in Jira. For example, in this case, it is a Task.
      • In the Jira Issue Type Category field, the category is populated depending on the selection in Jira. For example, in this case, it is a Standard Issue Type.
  6. Now, in Jira, create a Jira Issue Sub-Task under a Jira Task.
    1. Select Issue Type as Sub-task.
    2. Enter the summary for the Sub-task. For example, Kick-off meeting.
    3. [Optional] Enter the description of the Sub-task.
    4. Click Create.

      The connector automatically creates the Kick-off meeting in the PSA Project Task. Once the synchronization finishes, the Correlation ID field populates with the ID of the Sub-Task under a Jira Task in Jira. For example, NORTH-10.

      • In the Jira Parent Task field, the link to a PSA Project Task. This is the PSA Project Task that links to the parent issue in Jira. For example, in this case, the Jira Task is Scope writing.
      • In the Jira Issue Type field, the type is populated depending on the selection of the Issue Type field in Jira. For example, in this case, it is a Sub-task.
      • In the Jira Issue Type Category field, the category is populated depending on the selection in Jira. For example, in this case, it is Sub-Task Issue Type.

For more information on the Jira hierarchy, see the Atlassian documentation.

PSA Project structures are automatically updated in PSA to show Jira Issue PSA Direct for Jira Settings tab:

  • Sync PSA Projects to Jira
  • PSA projects to be mapped to Jira Issues
  • Sync Jira Issues to PSA Project Tasks
Note:

PSA Direct for Jira only updates the Jira hierarchy for the Jira Issue Type listed in the Jira Issue Type Settings. The name of the Jira Issue Type is case-sensitive and must be followed in the same way. Otherwise, PSA Direct for Jira fails the synchronization.

Before you start updating the PSA Project structure to show the Jira Issue hierarchy, ensure that you have enabled the Jira Parent Task field to be reflected in the PSA Project Task object via Upgrade PSA Direct for Jira feature in Feature Console. If you fail to do that, PSA Direct for Jira fails to update the PSA Project structure to show the Jira Issue hierarchy.

The example below assumes that you synchronize Jira Epics to PSA projects and have already set up a synchronized Epic in Jira.

To update PSA Project structure to show Jira Issue hierarchy:

  1. In Jira, create a Jira Task under the Epic that is synchronized to a PSA project. For this example, the Jira project has a key of SOUTH and the Epic name is Feature Development.
  2. Select Issue Type to Task and enter summary. For example, Environment Setup.
  3. [Optional] Enter the description of the Task.
  4. By default, the Epic Link is populated with Feature Development.
  5. Click Create.

    The connector automatically creates the Environment Setup in the PSA Project Task. Once the synchronization finishes, the Correlation ID field populates with the ID of the Task under Epic in Jira. For example, SOUTH-2.

    Note:
    • In this case, the Jira Parent Link is not populated because the Jira Task is at the top of the hierarchy. However, the task is created under PSA Project.
    • In the Jira Issue Type field, the type is populated depending on the selection of the Issue Type field in Jira. For example, in this case, it is a Task.
    • In the Jira Issue Type Category field, the category is populated depending on the selection in Jira. For example, in this case, it is a Standard Issue Type.
  6. Now, in Jira, create a Jira Issue Sub-task under a Jira Task.
    1. Select Issue Type as Sub-task.
    2. Enter the summary for the Sub-task. For example, Repository permissions.
    3. [Optional] Enter the description of the Sub-task.
    4. Click Create.

      The connector automatically creates the Repository permissions in the PSA Project Task. Once the synchronization finishes, the Correlation ID field populates with the ID of the Sub-task under a Jira Task in Jira. For example, SOUTH-3.

      • In the Jira Parent Task field, the link to a PSA Project Task is populated. This is the PSA Project Task that links to the parent issue in Jira. For example, in this case, it is Environment Setup.
      • In the Jira Issue Type field, the type is populated depending on the selection of the Issue Type field in Jira. For example, in this case, it is a Sub-task.
      • In the Jira Issue Type Category field, the category is populated depending on the selection in Jira. For example, in this case, it is Sub-Task Issue Type.

For more information on the Jira hierarchy, see the Atlassian documentation.