After 4.0.0 upgrade - reporting no longer working

[0x4c6565]

Infos:

• Used Zammad version: 4.0.0-20
• Installation method (source, package, …): Docker
• Operating system: CentOS 7
• Database + version: zammad/zammad-docker-compose:zammad-postgresql-4.0.0-20
• Elasticsearch version: zammad/zammad-docker-compose:zammad-elasticsearch-4.0.0-20
• Browser + version: Firefox 89.0b7

Expected behavior:

• When attempting to view the reporting section, open/closed ticket counts should show

Actual behavior:

• When attempting to view the reporting section, open/closed ticket counts are no longer showing since upgrading to v4.0.0:

We upgraded this on the evening of 21/04/2021, which you can see in the drop on the graph

Steps to reproduce the behavior:

• View reporting
• Observe no open/closed ticket counts since upgrade

[0x4c6565]

I have been able to resolve this by rebuild ELK search index as described here:

Graph in the reporting of an admin user is emtpy

Your index seems to be broken or incomplete. Please reindex your Zammad, this might also fix the reporting issue. zammad run rake searchindex:rebuild You might also be affected by: https://github.com/zammad/zammad/issues/2809 (this is fixed with 3.2) https://github.com/zammad/zammad/issues/2517 (not yet fixed, just possibly, doesn’t need to be a fitting issue )

[MrGeneration]

The release notes do contain clear hints on technical requirements for Zammad 4.0 like the mandatory re-index after upgrading.

You can find all release notes here (so you don’t have to struggle next time again ):

News, Updates, Releases | Zammad