Documentation
Docs
Learn
Release Notes
  • English
  • Українська
Docs
Learn
Release Notes
  • English
  • Українська
  • Release Notes
  • 5.6.10
  • 5.6.9
  • 5.6.8
  • 5.6.7
  • 5.6.6
  • 5.6.5
  • 5.6.4
  • 5.6.3
  • 5.6.2
  • 5.6.1
  • 5.6.0
  • 5.5.6
  • 5.5.5
  • 5.5.4
  • 5.5.3
  • 5.5.2
  • 5.5.1
  • 5.5.0
  • 5.4.4
  • 5.4.3
  • 5.4.2
  • 5.4.1
  • 5.4.0
  • 5.3.42
  • 5.3.41
  • 5.3.40
  • 5.3.39
  • 5.3.38
  • 5.3.37
  • 5.3.36
  • 5.3.35
  • 5.3.34
  • 5.3.33
  • 5.3.32
  • 5.3.31
  • 5.3.30
  • 5.3.29
  • 5.3.28
  • 5.3.27
  • 5.3.26
  • 5.3.25
  • 5.3.24
  • 5.3.23
  • 5.3.22
  • 5.3.21
  • 5.3.20
  • 5.3.19
  • 5.3.18
  • 5.3.17
  • 5.3.16
  • 5.3.15
  • 5.3.14
  • 5.3.13
  • 5.3.12
  • 5.3.9
  • 5.3.6
  • 5.3.5
  • 5.3.3
  • 5.3.2
  • 5.3.1
  • 5.3.0
  • 5.2.14
  • 5.2.13
  • 5.2.12
  • 5.2.11
  • 5.2.10
  • 5.2.9
  • 5.2.5
  • 5.2.3
  • 5.2.2
  • 5.2.1
  • 5.1.1
  1. Docs
  2. /Release Notes
  3. /Release 5.3.28

Release 5.3.28

What Changed

  • Touch norms and overwork. Daily touch norm history, overwork stats dialog, and extended period selection for reports.
  • Ticket status in reports. When a ticket status changes, reports show the current state.
  • Email threading. Improved email threading — correct behavior with Gmail and new ticket creation from emails.
  • Attachments in emails. Emails and PDFs now display all attachments — the operator sees all files.
  • Distribution limits. Chat distribution limits and queue verified — predictable assignment.
  • Email subject. Subjects are formed correctly; "Re:" is added only on reply.

How It Changed

Tickets and email

Before: Reports could show outdated ticket status; email threads could be wrong; attachments might not show.
Now: Reports show current state; emails thread correctly; attachments are displayed.
Why it matters: Accurate ticket reports and full email context in the Operator Panel.

Distribution and subjects

Before: Distribution limits might not be enforced; email subjects could be incorrect.
Now: Distribution limits and queue work correctly; email subjects are formed properly.
Why it matters: Fair workload distribution and clear email correspondence.

Prev
5.3.29
Next
5.3.27

On this page