Content
View differences
Updated by Andrej Sandorf 3 days ago
Steps are necessary to avoid
* <mention class="mention" data-id="78058" data-type="work_package" data-text="##JIM-152" data-display-id="JIM-152">##JIM-152</mention>
* <mention class="mention" data-id="79711" data-type="work_package" data-text="##JIM-213" data-display-id="JIM-213">##JIM-213</mention>
* Missing creation and update timestamps for imported issues
To fix:
* set work\_package **update\_at** **work\_package.update\_at** to **updated** from Jira
* set work\_package **created\_at** **work\_package.created\_at** to **created** from Jira
* add a new journal entry with migrated datetime of the migration
* suppress journal entries created by a later stage for attachment migration
* set the date of all migrated attachments to their creation the created datetime from Jira
* ensure work package creation datetime and all journal entries datetime to be
* ordered chronologically chronologically
* unique (journal requirement) by adding microseconds if they are equal (not visible in UI)
<br>
* <mention class="mention" data-id="78058" data-type="work_package" data-text="##JIM-152" data-display-id="JIM-152">##JIM-152</mention>
* <mention class="mention" data-id="79711" data-type="work_package" data-text="##JIM-213" data-display-id="JIM-213">##JIM-213</mention>
* Missing creation and update timestamps for imported issues
To fix:
* set work\_package **update\_at**
* set work\_package **created\_at**
* add a new journal entry with
* suppress journal entries created by a later stage for attachment migration
* set the date of all migrated attachments to their creation
* ensure work package creation datetime and all journal entries datetime to be
* ordered chronologically
* unique (journal requirement) by adding microseconds if they are equal (not visible in UI)
<br>