https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292017-06-02T11:42:01ZRedmineRedmine - Feature #25799: Issue Import - Dynamic Parent paskshttps://www.redmine.org/issues/25799?journal_id=789872017-06-02T11:42:01ZMischa The Evil
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Needs feedback</i></li><li><strong>Assignee</strong> set to <i>Robert Barnebeck</i></li></ul><p>Robert Barnebeck wrote:</p>
<blockquote>
<p>[...] 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.</p>
<p>Useful would be a kind of dynamic link between the issues. [...]</p>
</blockquote>
<p>I think you can already achieve such with the current implementation for <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Import Issues from delimited/CSV file (Closed)" href="https://www.redmine.org/issues/950">#950</a>.</p>
<hr />
<p>From <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Defect: Unable to import values for parent task (Closed)" href="https://www.redmine.org/issues/23396#note-2">#23396#note-2</a>:</p>
<blockquote>
<p>Jean-Philippe Lang wrote:</p>
<blockquote>
When importing issues, the content of a the parent colum can be:
<ul>
<li>a number without # (eg: 10) => the parent will be the 10th imported issue</li>
<li>a number with # (eg: #10) => the parent will be the existing issue with id=10</li>
</ul>
</blockquote></blockquote>
<p>and from <a class="wiki-page" href="https://www.redmine.org/projects/redmine/wiki/HowTo_import_issues#Parent-Issue">HowTo_import_issues#Parent-Issue</a>:</p>
<blockquote>
<p>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</p>
</blockquote>
<hr />
<p>So, a CSV file looking like follows (note the parent column values with the #-sign omitted):</p>
<table>
<tr>
<td>Subject</td>
<td>Startdate</td>
<td>Duedate </td>
<td>Parent</td>
</tr>
<tr>
<td>taskA </td>
<td>1/1/2016 </td>
<td>12/31/2016</td>
<td> </td>
</tr>
<tr>
<td>taskB </td>
<td>1/1/2016 </td>
<td>12/31/2016</td>
<td><code>1</code> </td>
</tr>
<tr>
<td>taskC </td>
<td>1/1/2016 </td>
<td>12/31/2016</td>
<td><code>1</code> </td>
</tr>
<tr>
<td>taskD </td>
<td>1/1/2016 </td>
<td>12/31/2016</td>
<td><code>3</code> </td>
</tr>
<tr>
<td>taskE </td>
<td>1/1/2016 </td>
<td>12/31/2016</td>
<td><code>3</code> </td>
</tr>
<tr>
<td>taskF </td>
<td>1/4/2016 </td>
<td>12/31/2016</td>
<td><code>4</code> </td>
</tr>
</table>
<p>would be imported creating the following issues tree:<br /><pre>
taskA
-> taskB
-> taskC
-> taskD
-> taskF
-> taskE
</pre></p>
<p>And, starting with not-yet-released Redmine <a class="version" href="https://www.redmine.org/versions/119">3.4.0</a>, you can even use a CSV file like:</p>
<table>
<tr>
<td>Subject</td>
<td>Startdate</td>
<td>Duedate </td>
<td>Parent</td>
</tr>
<tr>
<td>taskF </td>
<td>1/4/2016 </td>
<td>12/31/2016</td>
<td><code>2</code> </td>
</tr>
<tr>
<td>taskD </td>
<td>1/1/2016 </td>
<td>12/31/2016</td>
<td><code>5</code> </td>
</tr>
<tr>
<td>taskE </td>
<td>1/1/2016 </td>
<td>12/31/2016</td>
<td><code>5</code> </td>
</tr>
<tr>
<td>taskB </td>
<td>1/1/2016 </td>
<td>12/31/2016</td>
<td><code>6</code> </td>
</tr>
<tr>
<td>taskC </td>
<td>1/1/2016 </td>
<td>12/31/2016</td>
<td><code>6</code> </td>
</tr>
<tr>
<td>taskA </td>
<td>1/1/2016 </td>
<td>12/31/2016</td>
<td> </td>
</tr>
</table>
<p>which would be imported creating the following issues tree (equal to the example above):<br /><pre>
taskA
-> taskB
-> taskC
-> taskD
-> taskF
-> taskE
</pre><br />This extended feature behaviour is implemented through a separated issue (<a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Allow forward reference to parent when importing issues (Closed)" href="https://www.redmine.org/issues/22701">#22701</a>).</p> Redmine - Feature #25799: Issue Import - Dynamic Parent paskshttps://www.redmine.org/issues/25799?journal_id=794142017-06-23T08:20:54ZRobert Barnebeck
<ul></ul><p>Hi Mischa,</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>Best regards,<br />Robert</p> Redmine - Feature #25799: Issue Import - Dynamic Parent paskshttps://www.redmine.org/issues/25799?journal_id=796102017-07-01T14:36:55ZToshi MARUYAMA
<ul><li><strong>Status</strong> changed from <i>Needs feedback</i> to <i>Closed</i></li><li><strong>Assignee</strong> deleted (<del><i>Robert Barnebeck</i></del>)</li><li><strong>Resolution</strong> set to <i>Invalid</i></li></ul><p>Robert Barnebeck wrote:</p>
<blockquote>
<p>Maybe there would be a little improvement useful:...</p>
</blockquote>
<p>Please create new feature request issue.</p> Redmine - Feature #25799: Issue Import - Dynamic Parent paskshttps://www.redmine.org/issues/25799?journal_id=796112017-07-01T14:42:24ZToshi MARUYAMA
<ul><li><strong>Resolution</strong> changed from <i>Invalid</i> to <i>Duplicate</i></li></ul> Redmine - Feature #25799: Issue Import - Dynamic Parent paskshttps://www.redmine.org/issues/25799?journal_id=796122017-07-01T14:42:32ZToshi MARUYAMA
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/22701">Feature #22701</a>: Allow forward reference to parent when importing issues</i> added</li></ul> Redmine - Feature #25799: Issue Import - Dynamic Parent paskshttps://www.redmine.org/issues/25799?journal_id=836302018-02-19T16:05:11ZMischa The Evil
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/28213">Feature #28213</a>: Support external ID when importing issues</i> added</li></ul>