Hi support team,
I have an issue when importing issues with csv importer.
When i import sub-task i would like to import links sub-task to parent issue.
In my case i can create sub-task from Bug.
When i chose "Child-Issue" issue link type on the mapping panel, the import is going well but the links are reversed. I mean, on issue screen it shows sub-task is parent-issue of Bug.
I tried to fix it creating a new issue link "Parent-issue".
It worked i see the link on the good way but it is not present on Sub-Tasks block but on Issue Links block.
Could you please tell me how i can manage this.
Thanks
You should not be using the issue link field. Instead, you should be configuring it as follows:
You can create subtasks of issues through a CSV file import by encapsulating this structure in your CSV file. To do this:
The CSV file must have two additional columns whose headings should be named similarly to Issue ID and Parent ID.
Ensure that each regular (non subtask) issue is given a unique (sequential) number in the Issue ID column. Do not include any value in the Parent ID fields for regular issues.
To create a subtask of a regular issue in your CSV file, reference the unique Issue ID number of the regular issue in the Parent ID column. Don't set any value in the Issue ID fields for subtasks.
For example:
IssueType, Summary, FixVersion, FixVersion, FixVersion, Component, Component, Issue ID, Parent ID, Reporter
Bug, "First issue", v1, , , Component1, , 1, , jbloggs
Bug, "Second issue", v2, , , Component1, Component2, 2, , fferdinando
Bug, "Third issue", v1, v2, v3, Component1, , 3, , fferdinando
Sub-task, "Fourth issue", v1, v2, , Component2, , , 2, jbloggs
In this example, the fourth issue will be imported as a subtask of the second issue, assuming you match the "Issue ID" and "Parent ID" fields in your CSV file to the Issue ID and Parent ID Jira fields respectively during the CSV file import wizard.
This is found in the csv import documentation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.