~~Right now, if a work package is created by the Jira importer, the created date of the work package is set to the timestamp of the migration. The original value of the "creation date“ in Jira is lost. According to~~ ~~@Andrej Sandorf~~  ~~this was done on purpose, but we cannot recall the exact reason and would like to reconsider this choice.~~

~~@Wieland Lindenthal~~ ~~@Pavel Balashou~~  ~~Can you shed light on the previous decision?~~

* set **work\_package.update\_at** to **updated** from Jira

* set **work\_package.created\_at** to **created** from Jira

* add a journal entry with migrated datetime

* suppress journal entries created by a later stage for attachment migration

* set the date of all migrated attachments to the created datetime from Begin of the insertionJira

* ensure work package creation datetime and all journal entries datetime to be ordered chronologically and uniquely (journal requirement)End of the insertion Begin of the deletion Jira End of the deletion


Begin of the insertionThese steps are all 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>End of the insertion Begin of the deletion <br>End of the deletion

Begin of the insertion<mention class="mention" data-id="79711" data-type="work_package" data-text="##JIM-213" data-display-id="JIM-213">##JIM-213</mention>End of the insertion Begin of the deletion <br>End of the deletion