Bulk import of issues from CSV - how to maintain correct sequence + missing story points mapping

[Prem Mariappan]

Hi,

We have a CSV file of standard issues which we import into each new GH/Scrum project. The issues are ordered sequentially in the CSV file. However I notice that after the import, the stories are out of order. So I have to manually reprioritize them to get them in the right order.

How can I import and yet maintain the sequence?

Also, I notice that there isn't a Story Points field in the mapping phase of the import. I have to create a Story Points custom field to map top the corresponding column in the CSV file. I read that it is possible to have the Story Points field visible by making it a 'globally visible' - how do you do that?

Thanks very much.

Prem.

[Tom Corcoran · Accepted solution]

You can setup the csv column to have a Pr# column where the order is listed. In GreenHopper you can then edit one of the project contexts to show the issues in Pr# order.

[Renjith Pillai]

Prem, does the CSV file include also the ranking column that is used in GH for sorting? I am just guessing that if this is present you can keep the sort order same as in CSV. But am not sure whether it can be used since there are chances that the ranking gets a conflicting value while importing.

[Prem Mariappan]

A good point Renjith. I was thinking about including it but was hesitant for the same reason you point out. Multiple projects are sharing the same rapid board. And the same standard issues are being imported for each project. An issue that is imported into each project would have the same rank value - I wonder how GH/JIRA would deal with it?

[Renjith Pillai]

You should just go ahead and try in on a staging Jira server :) You mentioned Rapidboard, but your original question says importing when ever a new project is created. Do you really need Rapidboard or isn't the original GH is sufficient as you don't need prioritization across projects.

[Prem Mariappan]

We want to standardize our processes & procedures, and since Rapid Boards will eventually replace Planning/Task boards, we'd rather be standardizing on them. That's why we'd like to get things working right with Rapid Boards.

Will have to experiment with the ranking field.

Thanks Renjith.