You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
We adjusted the timeline of a recent incident in-line with our Tech. Provider yesterday, however, the updates are not yet reflected after +12 hrs and the outage still suggests 8h 39m, when it should now be 3hrs.
Can you explain why there is such a delay, please?
Ref. https://gladly.statuspage.io/incidents/wfhtw26h5vb3 // https://gladly.statuspage.io/
Thank you!
Hi Alex,
The component's historical uptime needs to be updated separately from the incident itself. Because component uptime can be linked to more than one incident it doesn't necessarily correlate perfectly with the incident timeline in all cases.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.