Why is the Conditional Fields app erasing previously set ticket field data?
Changing a preceding condition removes the information from subsequent fields in the ticket. This is expected behavior because the subsequent fields technically did not exist at the time of the ticket update.
As a workaround, consider creating a trigger to set these values after an agent updates the ticket. Otherwise, you can migrate your conditions from the app to the conditional fields feature in Support where this behavior is not present.