Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,466,638
Community Members
 
Community Events
176
Community Groups

Questions about dates and notice when creating incidents

I'm currently trying out the evaluation version, and I've seen some behavior that is different from what I expected, so I'd like to ask a question.

 

1. For some reason, an incident created by the API on Oct 17 02:15 Japan time is displayed as Oct 16 02:15.
Why is this? By the way, is there any way to rewrite the creation time with an arbitrary value?

 

statuspage-incidents.png

 


2. I was unable to receive email even though I was subscribing to an email during the time the incident occurred and until it was resolved. If the incident occurred for an extremely short period of time (e.g. when it was resolved in 1 minute), is it possible that the email was not received?

Is there anything I need to do to make sure I receive notifications even if the incident is only for a short time?

1 answer

1 accepted

2 votes
Answer accepted
Abraham Atlassian Team Oct 18, 2021

Hey Yuske,

 

Abraham here with Statuspage support. Thanks for reaching out.

The time difference here might actually be a bug so thanks for bringing that up. Would you mind opening a ticket with us at https://support.atlassian.com/statuspage/ and report this time discrepancy in there? 

As far as the notification issue, it might have been that you did not pick an affected component when creating the incident. We will only send notifications if an affected component it picked upon creation of the incident. 

Cheers,

- Abraham 

Thanks for the reply.
I'll make sure to report the time difference issue in the ticket.
I'll double check the notification issue.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events