Thanks :) that is helpful.
seeing the example in the page for subtask.
Does it mean i need to have each subtask as separate row?
You can create sub-tasks of issues by adding two columns to your CSV file with the headings "Issue Id" and "Parent Id".
- Give each parent issue a unique, sequential number in the Issue Id column. Leave the Parent Id column blank.
- For each subtask, put the parent issue number in the Parent Id column. Leave the Issue Id column blank.
In this example, the fourth issue is a sub-task of the second issue because its Parent Id matches the second issue's Issue Id:
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
because while creating automatic CSV in pivotal tacker, it has all the task in same row associating it with the user story.
Here is link for pivotal excel export - https://www.pivotaltracker.com/help/articles/csv_import_export/
If I need to keep all story task (subtask in JIRA) in new row for each story. Then I need to manually create the excel sheet to feed this information in JIRA
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs