Content
View differences
Updated by Henriette Darge almost 5 years ago
### **Environment**:
Your OpenProject Version: 11.2.2 / on premise
Windows 10 20H2 / MS Edge / OpenProject language: DE
### **Logs**
Are there errors in the browser console? ([Click here for information on how to open your browser's console](https://webmasters.stackexchange.com/a/77337)) For a local installation: Are there relevant logs output by `openproject logs` (packaged installation) ([click here for details](https://docs.openproject.org/installation-and-operations/operation/monitoring/#show-logs)) or in a log/production.log or /var/log/openproject/ ? Please attach error output in these log files if applicable
### **Steps to reproduce:**
I have a work package with three custom fields. I moved it from version 37 1. Go to version 38. page X
2. Click on button Y
3. Select Foo
### **Actual Behavior**
In this case, it adds a weird history entry to Describe the ticket, that I have changed the field "Version" and that I have removed all data from the fields "Leistungs-Nr.", "Produkt-ID" and "Projekt-ID" (all custom fields). But, the data is still there and I haven't done something like this. behavior you're seeing.
### **Expected Behavior**
I would expect a correct history entry, just with Describe the change in field "Version". expected behavior.
Your OpenProject Version: 11.2.2 / on premise
Windows 10 20H2 / MS Edge / OpenProject language: DE
###
Are there errors in the browser console? ([Click here for information on how to open your browser's console](https://webmasters.stackexchange.com/a/77337)) For a local installation: Are there relevant logs output by `openproject logs` (packaged installation) ([click here for details](https://docs.openproject.org/installation-and-operations/operation/monitoring/#show-logs)) or in a log/production.log or /var/log/openproject/ ? Please attach error output in these log files if applicable
###
I have a work package with three custom fields. I moved it from version 37
2. Click on button Y
3. Select Foo
### **Actual Behavior**
In this case, it adds a weird history entry to
### **Expected Behavior**
I would expect a correct history entry, just with