CSV import-How can I import some tasks under an existing task when doing a CSV import?

Anita Chen

Hi All,

 

I have few questions about the CSV import. Hope somebody can help me.

 

1. Can I import some tasks (child) under an existing task (parent)?  The link between them will be "contains in/ is contained in". When I import the CSV, I can't find the link of "is contained in" when I mapping the field.

 

2.  I imported some issues as "sub-task" under "Task A" (parent). After that, I do bulk moving, moving those "sub-task" to "task". However, those tasks can't be under the "Task A". Is that any way to keep those tasks under the "Task A" as when they were "sub-task"?  (Keep their parent issue to be the same, the link will be "contains in/ is contained in")

 

3. Some tasks (Key:ANITATEST-2/3/4)are under one epic(Key:ANITATEST-1). If move the epic(Key:ANITATEST-1) to be task, the hierarchy of all tasks (Key:ANITATEST-1/2/3/4)will be at same level. Is there any way to keep the hierarchy as the same?  (Key:ANITATEST-1 still be the parent issue and ANITATEST-2/3/4 be the child issues?)

 

4. Is there any way to move some issues under one task at one time? For example:Move three tasks to be the child of one task. The link between them is "contains in/ is contained in".

 

 

Trudy P Claspill

Hello @Anita Chen 

1. The name you will see in this list will be the name of the link relationship as shown in

https://<yourURL>/secure/admin/ViewLinkTypes!default.jspa

For instance for issues linked with "clones/is cloned by" the Name is Cloners. You need to find the Name that goes with your "contains in/is contained in" link relationship. I'm assuming that is a custom link relationship defined in your instance, as it is not one that is native to Jira.

2. No, there is no way to convert a sub-task to a task and maintain the parent/child relationship that Jira recognizes. The native issue hierarchy for Jira is

Epic > Story/Bug/Task/general issue > Sub-task

Issue types in the middle level can not be "children" of each other in the manner that Jira recognized Sub-tasks as children of other issues. You could create a custom generic link between them to imply a parent/child relationship, but Jira would not inherently recognize them as parent and child.

3. No. See my answer to #2. 

4. There is not a way to Bulk Change generic issue links, and the relationship you are talking about can be done only with a customized generic issue link.