Feature #25799: Issue Import - Dynamic Parent pasks - Redmine

Custom queries

Documentation issues
Open defects
Open features
Patch queue
Plugin issues
Translation patches

Actions

Copy link

Feature #25799

closed

Issue Import - Dynamic Parent pasks

Added by Robert Barnebeck almost 9 years ago. Updated over 8 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Importers

Target version:

Resolution:

Duplicate

Description

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.

Related issues

	Related to Redmine - Feature #28213: Support external ID when importing issues	Closed	Jean-Philippe Lang				Actions
	Is duplicate of Redmine - Feature #22701: Allow forward reference to parent when importing issues	Closed	Jean-Philippe Lang				Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Mischa The Evil almost 9 years ago

Status changed from New to Needs feedback
Assignee set to Robert Barnebeck

Robert Barnebeck wrote:

[...] 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.

From #23396#note-2:

Jean-Philippe Lang wrote:

When importing issues, the content of a the parent colum can be:

a number without # (eg: 10) => the parent will be the 10th imported issue

a number with # (eg: #10) => the parent will be the existing issue with id=10

and from HowTo_import_issues#Parent-Issue:

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:

taskA
 -> taskB
 -> taskC
     -> taskD
         -> taskF
     -> taskE

And, starting with not-yet-released Redmine 3.4.0, you can even use a CSV file like:

Subject	Startdate	Duedate	Parent
taskF	1/4/2016	12/31/2016	`2`
taskD	1/1/2016	12/31/2016	`5`
taskE	1/1/2016	12/31/2016	`5`
taskB	1/1/2016	12/31/2016	`6`
taskC	1/1/2016	12/31/2016	`6`
taskA	1/1/2016	12/31/2016

which would be imported creating the following issues tree (equal to the example above):

taskA
 -> taskB
 -> taskC
     -> taskD
         -> taskF
     -> taskE

This extended feature behaviour is implemented through a separated issue (#22701).

Actions

Copy link

Updated by Robert Barnebeck over 8 years ago

Hi Mischa,

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

Actions

Copy link