Closed StefanAbel-OTOBO closed 5 days ago
ov139 10.1.6
For dynamic fields which do not have a default value, hiding them and then showing them again is supposed to empty them. To me your description sounds like it works as intended. Only with "You see that the DF disappears from the window, but it still has its value (which is the correct behaviour)" I don't understand why you write that "it still has its value"?
but when you show it and it already has a value stored, imho that stored value should be shown in the DF. In case this is intended, I feel okay with closing the bug, but for me it doesn't feel like the correct behaviour.
Is the discussion on this topic still open or can this issue be closed?
Nothing new so far, closing the issue.
When creating a DF Database and hiding it with an ACL (Possible Not > Ticket Form) under some circumstances, it seems empty when displaying it again.
Step 1: Create a DF Database and make it work
Step 2: Create two ACLs to hide the DF Database in some situations (here depending on the Ticket Type "RfC") and
Step 3: Create a ticket with a value in the DF Database
Step 4: Change the prerequesite so that the DF Database will be hidden according to your ACL (here: change the Type to not "RfC" and save it and You see that the DF disappears from the window, but it still has its value (which is the correct behaviour)
Step 5: Change the prerequesite so that the DF Database will be shown again according to your ACL (here: change the Type to "RfC" and see that in this window, the DF appears again - but without any value. You don't see a value in the DF, despite the fact that it has one (according to the Ticket History and the Ticket Information). If you would now click on "Submit", it would delete the value, which might cause quite the problems if you still expect your value.
My expectation would be that if you show the field again, it should display it's stored value.