要約

Jira's External System Import tool allows the creation of sub-tasks without a parent issue. Once created, it's not possible to manually create (from Jira UI) the link between the orphan sub-tasks and the issues that are supposed to be their parents.

診断

You can use the JQL query below to find orphan sub-tasks on your site.

type = Sub-task AND parent is EMPTY

If you try to use the option Convert to issue in an orphan sub-task, an error message will appear saying that the issue is not a sub-task.

原因

This happens when sub-tasks are imported to Jira via CSV and the references to parent issues are not present in the file.

ソリューション

It's possible to fix this by importing a new CSV file to create the link between the orphan sub-tasks and their parents.

To achieve that, you must Import data from a CSV file, using the following file structure:

IssueKey,IssueType,Summary,IssueId,ParentId
ITMS-48,,,1,
ITSM-49,,,2,
ITSM-47,,,,1
ITSM-46,,,,2

In this example, issues ITSM-48 and ITSM-49 are existing parent issues to which we are assigning the IDs 1 and 2, respectively. ITSM-47 is an orphan sub-task that will become a child of ITSM-48, and ITSM-46 will become a child of ITSM-49.

You can add multiple parents and sub-tasks to the file to fix multiple orphans at a time.

Note that all CSV and Jira fields must be correctly mapped for the solution to work.

Once the import is complete, both issues will be correctly associated.

To avoid this type of problem in the future, we have a feature request to prevent the creation of orphan sub-tasks:

JRACLOUD-42405 - 課題詳細を取得中... ステータス