Bug? in the history

  • Used Zammad version: 6.1.0-1700492762.96ac5a60.bionic
  • Used Zammad installation type: package
  • Operating system: Ubuntu 20.04.6 LTS
  • Browser + version: Newest Chrome

Expected behavior:

history doesnt say that former employees (agents) do changes to tickets right now

Actual behavior:

history says former employee right now did a change

Steps to reproduce the behavior:

Create a ticket and choose any customer.
Now disable your user and remove agent rights (like you are a former employee), then change the customer and after that delete the first customer.
After that is finished there will be a message in the history that the former employee right now edited the ticket to change the customer "from deleted customer to - "

Just saw it right now and thought you could be interested in fixing this. I think the right behaviour would be A) change the customer also in the first paragraph or B) change the history to “System changed” instead of “former employee changed”

That’s to be expected.
The history contains references to the users and these have to be removed before. To not loose these entries, Zammad sets user id 1 (which translates to system).

Other wise you wouldn’t be able to remove the user.
This is indirectly mentioned in the FAQ’s of the function as well:
https://admin-docs.zammad.org/en/latest/system/data-privacy.html#frequently-asked-questions

Hi @MrGeneration ,

I think you didnt understand me right.
If the history would say “System changed xxx” everything would be fine to me.
But instead it says “name of former employee changed xxx right now”. Thats what I feel shouldnt be right.
If history would say “system changed xxx right now” everything would be fine.

In the FAQ you mentioned I only found “The deletion will not consider historical assignments.”
From that I understand that zammad just doesnt care about new created history assignments right now.

Its not important to me, I just thought zammad would be interested in fixing this.
Its up to you…

You’re on Zammad 6.1. The issue you’re describing never occured to me.
Upgrade to 6.3.1 (which is the current stable) and check if this still occurs on new tickets. Existing entries most likely will not be fixed.