We use the issue import feature in Redmine when we have a new project. In every project there is a bunch of issues, which cover typical tasks (design, deployment, accounts, testing e.g.). These tasks are connecetd between each other via parent task. We´d like to connect the issues directly with the import. But we cannot insert the explicit issue number, because the parent issues don´t exist before import. And the second reason is that we want to us the import file as template, so there cannot be specific numbers.
Useful would be a kind of dynamic link between the issues. Maybe one column in the import file represents a local ID, which can be used for the dynamic parent task link.
[...] We´d like to connect the issues directly with the import. But we cannot insert the explicit issue number, because the parent issues don´t exist before import. And the second reason is that we want to us the import file as template, so there cannot be specific numbers.
Useful would be a kind of dynamic link between the issues. [...]
I think you can already achieve such with the current implementation for #950.
If the field starts with an #, the issue with that id is referenced. If the field contains a number it references the index of the issue in the import. Note that it's not the line number as line 1 contains the header
So, a CSV file looking like follows (note the parent column values with the #-sign omitted):
Subject
Startdate
Duedate
Parent
taskA
1/1/2016
12/31/2016
taskB
1/1/2016
12/31/2016
1
taskC
1/1/2016
12/31/2016
1
taskD
1/1/2016
12/31/2016
3
taskE
1/1/2016
12/31/2016
3
taskF
1/4/2016
12/31/2016
4
would be imported creating the following issues tree:
at first sorry for my late response. I didn´t notice the update mail. Thanks for your very informative information. I didn´t know the feature with the relating parent task, that is very helpful.
Maybe there would be a little improvement useful: We want to use ticket imports for new projects, where we have our standard tickets. But we don´t need all of these tickets for every new project. When deleting some rows, the relational row-link to the parent ticket can change. So it would help to relate to a defined ID-Column or something, where the ID doesn´t change, even if rows are deleted inbetween.
Do you think this would be an appropriate feature request? It seems that I´m not allowed to change assignee, so I hope my message will be received.
Best regards, Robert
Updated by Toshi MARUYAMA over 9 years ago
Actions