Idea #72355: Jira Import Chunk for 17.3

View differences

Updated by Wieland Lindenthal 4 days ago

This is the next iteration after <mention class="mention" data-id="65093" data-type="work_package" data-text="##65093">##65093</mention>

This EPIC is a collection of data objects that we thrive to support within our Jira import for the 17.3 release.

The goal is to get closer to fully migrate Jira projects/spaces. However, another iteration is likely needed after this one.

## Scope (might be flexibly adopted)

* Work item relations:

* Parent-Child

* Follow-Precedes

* Blocks / Is blocked by ==&gt; Blocks/Blocked-by

* Clones/Is cloned by ==&gt; Relates to

* Relates to &nbsp;==&gt; Relates to

* Custom link types

* &quot;required by&quot; ==&gt; &quot;requires&quot;

* Others we use &quot;relates to&quot; with a &quot;Description&quot; on the relation like

* &quot;implements&quot;

* &quot;causes&quot;

* &quot;required by&quot;

* &quot;causes&quot;

* ...

* Sprint assignments

* Requires <mention class="mention" data-id="59553" data-type="work_package" data-text="##59553">##59553</mention>

* Work item identifiers

* Requires <mention class="mention" data-id="71626" data-type="work_package" data-text="##71626">##71626</mention>

* Versions

* Requires <mention class="mention" data-id="71752" data-type="work_package" data-text="##71752">##71752</mention>

* Custom fields

* Probably a subset as it depends on what custom fields are available in Jira and which in OpenProject.

<br>

Back

Content

View differences