Summary
When multiple events are recorded on the same day within repeatable program stages of any tracker program and then synced, the system incorrectly records all events as occurring at the same time (00:00). This makes it impossible to determine the chronological order of events, affecting calculations and program rules that rely on accurate timestamps.
Environment
DHIS2 Version: 2.40
Android Capture App: Version 3+
Platforms Affected: All platforms (Android devices and web browsers)
Applications Affected: Both Capture App and Tracker Capture in browser
Steps to Reproduce
Open any tracker program with repeatable program stages
Create multiple events within the same repeatable stage on the same day
Record these events with the same date
Sync the data (if using mobile) or save the data (if using browser)
View the events in the system
Current Behavior
After synchronization/saving, all events created on the same day within a repeatable program stage appear with identical timestamps (same date with time set to 00:00), regardless of when they actually occurred. This makes it impossible to determine which event happened first and which happened last.
Expected Behavior
Each event should maintain its unique “OCCURRED AT” timestamp after synchronization/saving, preserving the chronological sequence of events and allowing proper calculations based on event order.
Impact
Calculations using program rules are not working correctly because the system cannot determine the proper sequence of events.
It’s impossible to establish the chronological order of events occurring on the same day.
This affects all tracker programs where the sequence of events matters, including:
Pharmacy stock management (cannot determine transaction order)
Any program where multiple activities need to be tracked in sequence on the same day
Technical Details
The issue occurs consistently on all platforms and affects both the Capture App and Tracker Capture interfaces in the browser. When multiple events are recorded with the same date but different times in a repeatable program stage and then saved/synced, the system ignores the time component, defaulting all events to 00:00 for the time value.
Scope of the Issue
This issue affects all tracker programs with repeatable stages where multiple events can occur on the same day. The time component (hours, minutes, seconds) is critical for establishing the correct sequence of events, especially when multiple events happen within the same 24-hour period.
Reproducibility
Consistently reproducible in any tracker program with repeatable stages when recording multiple events on the same day followed by synchronization or saving.
Additional Information
This issue has significant impacts on any program that requires chronological tracking of events. Without the ability to determine the sequence of events occurring on the same day, many program rules and calculations become unreliable or impossible to implement correctly.
