Content
View differences
Updated by Wieland Lindenthal 8 days ago
What happens if OpenProject (converted to semantic identifiers) and JIRA share the same project identifier? How/where do we handle that conflict?
**Initial idea:**
Initial idea: Have the JIRA Import Tool migrator detect conflicts and show them before confirming their import. It really depends on a case by case situation what the migrating user prefers.
Sometimes the Jira project holds more value than the existing OpenProject. Then, the importing user would chose to move OpenProject's project error out of the way, first. So that the history of the Jira project is kept intact.
Or the OpenProject project holds more value. Then a solution would be to first rename the project on the Jira side, first, so that it can be imported without conflicts.
them. 
In any case further iterations, we probably should never import historic identifiers from Jira that collide with current or historic identifiers in OpenProject. We probably need to accept the loss.
What we could consider, though, is offer some ways to add reconcile this automatically.
The conflicts should likely be detected _before_ the Jira's historic identifiers as searchable strings instance gets converted to the imported objects. So that when we search in OpenProject for an identifier, e.g. with the `typeahead` filter, then it could find multiple results, instead of clearly only one. semantic identifiers.
**Initial idea:**
Sometimes the Jira project holds more value than the existing OpenProject. Then, the importing user would chose to move OpenProject's project
Or the OpenProject project holds more value. Then a solution would be to first rename the project on the Jira side, first, so that it can be imported without conflicts.
What we could consider, though, is
The conflicts should likely be detected _before_