[Uganda project - Technoforte team] Time field auto-populates with 00:00 on interaction in v1.9.6 (regression from v1.9.5)

[Abhay-Dev-Gautam]

Time field auto-populates with 00:00 on interaction in v1.9.6 (regression from v1.9.5)

---

Summary

After upgrading from v1.9.5 to v1.9.6, we observed a regression in the behavior of the TIME field.

If a TIME field is left untouched, it remains empty as expected. However, once the user interacts with the field (focus or click), the value is automatically set to 00:00. Even if the user tries to clear the value, it is immediately restored back to 00:00.

This behavior was not present in v1.9.5.

---

Environment

• OpenCRVS Core version: v1.9.6
• Previous working version: v1.9.5
• Browser: Chrome / Firefox
• Form type: Birth / Death declaration
• Field type: FieldType.TIME

---

Steps to Reproduce

1. Configure a form with a FieldType.TIME field.
2. Load the form and do not interact with the time field.
   • The field remains empty (expected).
3. Click or focus on the time field.
   • The value is automatically populated as 00:00.
4. Attempt to delete or clear the value.
   • The value is immediately restored to 00:00.

---

Expected Behaviour

• The TIME field should remain empty unless a value is explicitly provided by the user.
• Clearing the TIME field should persist an empty value.
• The field should not auto-populate unless explicitly configured with a default value.

---

Actual Behaviour

• Interacting with the TIME field automatically sets the value to 00:00.
• Clearing the field does not persist; the value is restored automatically.
• Users are unable to leave the TIME field empty once it has been interacted with.

---

Regression Observation

This issue does not occur in v1.9.5.

While comparing v1.9.5 and v1.9.6, we noticed new logic related to TIME field default value resolution (similar to DATE fields, e.g. $$now) introduced in v1.9.6. The regression appears to be related to these changes.

---

Additional Context

• The issue occurs even when no explicit defaultValue is configured for the TIME field.
• The behavior is consistent across browsers and forms.
• This impacts users who do not know or do not wish to provide a time value.

---

Clarification Requested

• Is the TIME field expected to auto-populate on interaction in v1.9.6?
• Is this behavior intentional or an unintended side effect of recent TIME field changes?
• Is there a recommended workaround or configuration to preserve the v1.9.5 behavior?

[euanmillar]

@Abhay-Dev-Gautam this has been classified as a medium (non-blocking) priority issue. It will be resolved in a hotfix at some point in the next few months: #11751