All open tickets will be changed

Technical assistance
1

Infos:

  • Used Zammad version: 6.3.1
  • Used Zammad installation type: Kubernetes (zammad 12.4.1 · zammad/zammad)
  • Operating system: AWS EKS 1.30
  • Browser + version: Firefox 131

Expected behavior:

Tickets should not change their “last chaged” timestamp.

Actual behavior:

I have a problem that all open tickets will be changed from some magic. You can’t see any change in the ticket, but the “last change” timestamp changed.

This results in the problem that our “first in first out” workflow won’t work anymore.

I can see this in the logs when the tickets are getting updated:

I, [2024-10-09T13:08:24.295805#1-149160]  INFO -- : 2024-10-09T13:08:24+0000: [Worker(host:zammad-scheduler-8697b7f4cc-mdnc8 pid:1)] Job SearchIndexAssociationsJob [98131742-887f-47ef-aa53-8fc1ed44277b] from DelayedJob(default) with arguments: ["Ticket", 13041] (id=5497852) (queue=default) RUNNING

I don’t know how to reproduce the problem, but I think this can be an ElasticSearch problem?

Does anybody has an idea?

2

Use last contact.

naaah

I bet you’re using Service Level Agreements

1 Like
3

Yes, we use SLA.
Why does SLA such side effects?

I will try to change to “last contact”

4

Okay… “last contact” works for me. Thanks a lot.

1 Like
5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.