When users are entering historical log updates into the system, they are often confused by the event log. The confusion arises because events are currently sorted by the date and time they were triggered, rather than by the "measured at" timestamp entered by the users during the log update. This makes it difficult for users to distinguish between past data and the latest changes.
To Replicate
File a log update with the measured at date as today
File a log update with the measured at date as yesterday or any past date
See the events, it's currently sorted based on event creation date, which might be unintuitive for a normal user.
Screenshots
Suggested Solution
sort the events log date based on the "measured at" value
the field that doesn't have "measured at " value, sort them based on "created at" value
Describe the issue
When users are entering historical log updates into the system, they are often confused by the event log. The confusion arises because events are currently sorted by the date and time they were triggered, rather than by the "measured at" timestamp entered by the users during the log update. This makes it difficult for users to distinguish between past data and the latest changes.
To Replicate
measured atdate as todaymeasured atdate as yesterday or any past dateScreenshots
Suggested Solution
cc: @nihal467 @sainak @gigincg @aparnacoronasafe
Issue reported by athul doctor