Content
View differences
Updated by Wieland Lindenthal 8 days ago
Jira's components map best to OpenProject's "Categories" feature. Categories are also project specific, just as components in Jira. They also have a concept of a default assignee. They are the right fit.
In Jira, an issue can belong to multiple components. In OpenProject there can still be only one category per work package. This needs to change to multi-value before we can migrate <mention class="mention" data-id="78206" data-type="work_package" data-text="###COMMS-946" data-display-id="COMMS-946">###COMMS-946</mention>
Making OpenProject Categories behave even more like Jira's components (e.g. component responsible, description, ...) is not part of the first scope for the Jira Migrator. However, that is tracked here <mention class="mention" data-id="72780" data-type="work_package" data-text="###FND-37" data-display-id="FND-37">###FND-37</mention>
In Jira, an issue can belong to multiple components. In OpenProject there can still be only one category per work package. This needs to change to multi-value before we can migrate <mention class="mention" data-id="78206" data-type="work_package" data-text="###COMMS-946" data-display-id="COMMS-946">###COMMS-946</mention>
Making OpenProject Categories behave even more like Jira's components (e.g. component responsible, description, ...) is not part of the first scope for the Jira Migrator. However, that is tracked here <mention class="mention" data-id="72780" data-type="work_package" data-text="###FND-37" data-display-id="FND-37">###FND-37</mention>