Can the Epic>Story>Sub-task relationship be successfully imported into Greenhopper with a CSV file?

David Barrett

Hi,

I am trying to import an Excel spreadsheet of requirements into Greenhopper.

The import process runs successfully but when I check the scrum board, the Stories aren't linked with their Epics. Instead I see a field in Story called 'Epic/Theme' with the parent Epic name as a label.

Can the Epic > Story > Sub-task relationship be successufully imported into Greenhopper/Jira with a CSV file?

Here's the CSV file content:

Description,Summary,Issue Id,Parent Id,IssueType,Story Points,Epic,Component,Component,Component,Component,Component,Component,FixVersion,FixVersion,FixVersion,OriginalEstimate (s),Reporter
Description1,Epic1,,,Epic,,,component1,component2,component3,,,,0.1,,,,reporterName
Description2,Story1 for Epic1,101,,Story,1,Epic1,component1,component2,component3,,,,0.1,,,,reporterName
Description3,Sub-task1 for story1,,101,Sub-task,,Epic1,component1,component2,,,,,0.1,,,14400,reporterName
Description4,Sub-task2 for story1,,101,Sub-task,,Epic1,,,component3,,,,0.1,,,28800,reporterName
Description5,Sub-task3 for story1,,101,Sub-task,,Epic1,component1,component2,component3,,,,0.1,,,14400,reporterName

Renjith Pillai

Epic story relation is using something called as system link (it's a normal issue link, but hidden). I am not sure if you can import it via CSV. The Epic/Theme field is used by Classic modes and not used by the new boards of GH.

You have some alternatives to use REST to create issues and also link to stories. You need to be comfortable with a bit of scripting though

https://answers.atlassian.com/questions/115733/how-to-attribute-issue-to-epic-via-api