Hey, me again. Following your instructions I verified:
1) ticket printing works fine, custom user fields were already included in the export.
2) The problem is that in the update the content of the custom added fields was lost.
3) The structure of the tables was kept well, the custom aggregate fields are still defined.
But in the screen display of the tickets, these fields are "empty" after the update, so they are not printed.
I modified a ticket by adding a value in a custon aggregate field and then it comes out fine on print.
Checking possible solution:
I have a backup from 2 weeks ago with the values of the custom added fields with the v1.10 table structure, I need to pass the values of the custon added fields from the backup to the base in production.
First step: Recover the database backup with another name.
Second step: Extract the table with the values of the custom fields and copy it to the production database.
Third step: Manually load the values of the added custom fields from the last backup that will remain empty.
is this possible?
a) if the structure of the table where the values of the custom added fields are saved remains unchanged from version 1.10 to 1.15.8 (because if I update the structure of the table again by building another installation in v1.10 with the backup and update again to 1.15.8... I'm afraid that data will be lost again...)
b) if there may be problems due to leaving tickets without an entry in the table where the added custom fields are saved (tickets loaded from the last backup, although I imagine that if a ticket has no value in a custom field... that should not be published table with null values.)
Thanks again in advance for helping me solve this problem.