Creating incident not appearing on status page

[adamb53]

Version: 3.x dev demo
Issue details:

• After creating an incident and setting the "Occurred at" to today with any time, the incident does not appear on the status page
• Setting the incident to yesterday does make the incident appear
• It is possibly to do with me being in Australia, even though I set the timezone in Cachet to Melbourne/Australia

[jbrooksuk]

@adamb53 sorry for the delay in getting back to you, I've been on holiday.

I'll look into this shortly.

[jbrooksuk]

@adamb53 I was unable to replicate this issue on the v3.cachethq.io demo. Would you be able to provide any additional information as to the incident data you're providing or a video replicating this issue, please?

[jbrooksuk]

@Artic6 you posted this to the wrong thread.

[Artic6]

Good spot, you can close this one off anyway *Lee Croucher * *🐻*| ***@***.*** | w:https://a6n.co.uk <http://www.a6n.co.uk/> <http://facebook.com/artic6> <http://us.linkedin.com/in/artic6> <http://twitter.com/artic6> <http://flickr.com/photos/croucher_lee> <http://itunes.apple.com/app/artic6> <http://drive.google.com/artic6>

…

On Mon, 3 Jun 2024 at 05:50, James Brooks ***@***.***> wrote: @Artic6 <https://github.com/Artic6> you posted this to the wrong thread. — Reply to this email directly, view it on GitHub <#4389 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAD7S74X3VXHXLUJPIY6DALZFPY2TAVCNFSM6AAAAABIAPIJFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBUGI3TKNJTHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[adamb53]

@jbrooksuk No worries!
I just went to replicate and it's now showing a different outcome. Still not what is expected, but still points to the timezones being an issue.

Now what I am seeing is, that if I set the time to 3 PM, it is showing in the dashboard as 3 PM but says it is in 9 hours.
If I set the time back to 2 am, it shows 2 am in the dashboard but says it was 3 hours ago (again, it is 3 PM for me in my timezone, which is what Cachet is set to in the configuration options)

Is the intention is for the dashboard to show in UTC no matter what?

Here is a video to try to show what I just experienced. Pay attention to the time I set in the incident compared to the time in the dashboard and my PC time.

Screencast.from.03-06-24.15.05.23.webm

[Artic6]

I was definitely in UTC because that’s where we are, Could it also be the tick box that says showtime zone in your local zone regardless of what is set I’m just trying to figure out if someone puts an incident or maintenance task in the past is that going to break Cachet? *Lee Croucher * *🐻*| ***@***.*** | w:https://a6n.co.uk <http://www.a6n.co.uk/> <http://facebook.com/artic6> <http://us.linkedin.com/in/artic6> <http://twitter.com/artic6> <http://flickr.com/photos/croucher_lee> <http://itunes.apple.com/app/artic6> <http://drive.google.com/artic6>

…

On Mon, 3 Jun 2024 at 06:14, adamb53 ***@***.***> wrote: @jbrooksuk <https://github.com/jbrooksuk> No worries! I just went to replicate and it's now showing a different outcome. Still not what is expected, but still points to the timezones being an issue. Now what I am seeing is, that if I set the time to 3 PM, it is showing in the dashboard as 3 PM but says it is in 9 hours. If I set the time back to 2 am, it shows 2 am in the dashboard but says it was 3 hours ago (again, it is 3 PM for me in my timezone, which is what Cachet is set to in the configuration options) Is the intention is for the dashboard to show in UTC no matter what? Here is a video to try to show what I just experienced. Pay attention to the time I set in the incident compared to the time in the dashboard and my PC time. Screencast from 03-06-24 15:05:23.webm <https://github.com/cachethq/cachet/assets/8874130/1860a255-789a-474c-a581-6191791ed17e> — Reply to this email directly, view it on GitHub <#4389 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAD7S762HS5BP53UZLEIYZTZFP3T5AVCNFSM6AAAAABIAPIJFWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBUGI4TOMBWGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>