You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment we use the update.created_at timestamp next to comments, to show when they were posted. However, we don't include the actual began_at/ended_at timestamps.
This is particularly noticeable when historic incidents are added to the page, as their true start/end time isn't displayed, only the time the notice was added to the page.
The text was updated successfully, but these errors were encountered:
The first steps towards this were adding in 2.44.1 which just includes the began/ended timestamp alongside the duration in the "timeliness" section of the notice.
We'll next be looking at some style changes to updates to make the date/time they were posted less dominant.
While doing some more QA I actually found a bug in that last PR, and 2.44.1 so have reverted the changes until I get time to properly address it. 2.44.2 is the latest stable release, and matches 2.44.0.
At the moment we use the
update.created_at
timestamp next to comments, to show when they were posted. However, we don't include the actual began_at/ended_at timestamps.This is particularly noticeable when historic incidents are added to the page, as their true start/end time isn't displayed, only the time the notice was added to the page.
The text was updated successfully, but these errors were encountered: