I did more testing/troubleshooting, and i found out more:
- There are some openb tickets already created
- I new field with data integrity is set up and deployed
- Already open created ticket, behave as designed. They require the field with data integrity check to have data in them in order to be able to close them.
- New tickets created after data integrity field is setup and deployed, do no require the field to have data in it and you can proceed with closing them (not normal\desired behavior)
My fix here was to delete all tickets, create the new field with data integrity check and everything started to be ok afterwards. With the luck here that i am still testing OSticket V1.15.2 and is not in production YET.
BUT, let's imagine that we have the system already deployed in production and we want to introduce this new field with data integrity check. What option we have here to work as designed, without deleting all tickets ever?
As always, thank you in advance 🙂