1 of 1 people found this helpful
You could do a second field to set the initial value that you want then use a SQL script to ultimately copy the data from creation field 2 into creation date.
Thanks Jamie for your answer,
While the idea of utilizing a secondary field was perceived first as a very good alternative, it now brings big challenges:
1. SLA calculations happens at the moment of creating the Incident. Therefore, replacing later creation date would not update SLA calculations.
2. Process status is another field we would need to bring from the old ITSM tool. But again, replacing the field won't update the Actions, Assigns and Decisions that happen between Processes Statuses.
This starts to sound that we better manage calculations outside Service Desk.