Custom datetime attributes are always marked as changed


  • Used Zammad version: 3.6.0
  • Used Zammad installation source: source within custom Docker containers
  • Operating system: Host: Ubuntu 20.04, Docker containers based on ubuntu:20.04
  • Browser + version: Firefox 84.0.2 (on Ubuntu 20.04)

Expected behavior:

  • Custom datetime attributes are only marked as changed when they have actually been changed.

Actual behavior:

  • Custom datetime attributes are always marked as changed (which causes the user to always discard his changes on closing the tab, even if there haven’t been any changes).
    This problem seems to be exclusive for datetime attributes. All other custom attributes seem to work probably.

Steps to reproduce the behavior:

Additional information

The “Discard your unsaved changes” button is visible all the time as well.

Clicking it doesn’t seem to have any effect (the datetime attribute is still marked as changed).

Sorry for the wait.
If you haven’t already, please upgrade to Zammad 4.0.

I can’t reproduce it on a current stable installation.

I just setup a fresh and empty 4.0.0 installation to test the datetime fields and unfortunately the bug is still present.

I noticed a little detail though:
The bug only occures after the datetime field got a value for the first time.
If it isn’t a mandatory field and you don’t fill it at all, it’s ignored as expected.

Sorry I can’t reproduce that at all.
You did restart Zammad accordingly after updating the database?
Are you sure you’re not having some kind of weird cache on your installation?

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