csv import - move an standard issue-type to an Epic

markus.neuwald@canon.at

Hi!

we use JIRA for documentation of our pre-sales and installations.

now i created for each customername an epic and i want to move our pre-Sales Issues and Implementation Issues to that epic for each customer.

JIRA does not allow to directly move an standard issue-type to an epic -> first it is necessary to convert it to a sub-task, and within the tool i can set the new parent (epic).

As i have a lot of "standard-issues" to move to the correct epic, i want to use the csv Import to update each issue with the new parent (epic).

But i find no way to do it. 

How to configure the csv import to change the issue-type to subtask and move it to the new parent in one go?

my csv looks like:

issuekey; issue-ID; parent key; parent-ID; Summary; issue-type

CAT-5921; 45083; CAT-7528; 62924; uF_3E Handel; ST: PreSales Deal Support

The idea is that the csv import updates the issuekey "CAT-5921" and set the issue-type to "ST: PreSales Deal Support" and moves it as a child of "CAT-7528".

The import stopps with the information, that the issue CAT-5921 is no sub-task and so it will not be part of CAT-7528.

Should that work?

What have i done wrong?

Is there a tip on how to move several different tasks into different epics?

kind regards,

Markus

Trudy P Claspill

Hello markus.neuwald@canon.at 

Do I understand correctly that you have existing standard-type issues that you want to make children of existing Epic-type issues?

If so, there is a flaw in your reasoning.

JIRA does not allow to directly move an standard issue-type to an epic -> first it is necessary to convert it to a sub-task, and within the tool i can set the new parent (epic).

Jira absolutely allow you to set the parent of a standard-type issue to an existing Epic through the UI without converting it to a sub-task.

One method is to view the standard-type issue and click the Add Parent option in the breadcrumbs above the summary.

 

Another option is to ensure you have the Parent field included in the Layout of the issue and then click there to insert the key for the Epic.

 

With regard to the failure in the import process, we must first know a few things:

1. What type of project does this concern? Get that information from the Type column of the View All Projects page under the Projects > More Projects menu.

2. How exactly are you accessing the CSV import process? Are you accessing that through System > External System Import, or are you accessing it from the Search Work Items screen and selecting Import Work Items from CSV?

3. Show us a screen image of the field mapping you are creating when you execute this import.