aboutsummaryrefslogtreecommitdiff
path: root/layouts/issues/small.html
AgeCommit message (Collapse)Author
2023-05-18issues resolution time now aware of whether severity was `down` or notNathan Barton
2021-12-25fix #213Mantas Vilčinskas
2021-08-23Fix #199Mantas Vilčinskas
2021-07-24Fix relative date for resolved issues and non-UTC browser timezone. (#197)Harald Kraemer
* Remove Storehouse from the README examples (#195) Their status page is no longer present, as they seem to be changing their web strategy * Fix relative date for resolved issues and non-UTC browser timezone. The missing <UTC> in the layout causes a weird glitch if the users browser is in a non-UTC timezone. For open incidents, the time is rendered as "23-07-2021 12:17:40 UTC", and then the javascript library correctly translates from UTC into the users browser time, resulting in say "30m ago". For a resolved incident, the timezone of the date was stripped due to the missing <UTC> in the format string, resulting in "23-07-2021 12:17:40". If the user has a browser is in the timezone CEST (UTC+2), this causes the relative time to jump from "30 minutes ago" for an open incident to "2 hours ago" for a closed incident, because now the time without time zone is not interpreted as UTC anymore. Co-authored-by: Justin Clift <82353280+jc-dgit@users.noreply.github.com> Co-authored-by: Harald Kraemer <harald.kraemer@sabio.de>
2021-02-24Doc updates, bugfixes, add rel time to NCMSMantas Vilčinskas
2020-10-27add .Site.Params.useRelativeTimeKevin Hamer
2020-10-27Add .relative-time class and JS logicKevin Hamer
2020-04-12#102Mantas Vilčinskas
2019-12-15Design updates - dark mode finished, mini fixesMantas Vilčinskas
2019-10-04Added symbols for severity, informational posts, yearly layout defaultMantas Vilčinskas
2019-03-20Fix #64Mantas
2019-01-24cState is now stable on v3.0 - 2019-01-24 (info: #41)Mantas