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.
We are updating the component statuses through PagerDuty Integration. While doing so,
When a component is under Maintenance, an incident is created in PagerDuty through another external automation. Due to this, the status of the component in StatusPage is also changed/ over-written with this new status as Partial Outage.
While the status is in Active Maintenance, the component should not change any of its Statuses is my assumption. But it changes to Partial Outage as per the PagerDuty Integration Rule, when an incident occurs and goes back to Operational when it is resolved. Though it doesn't go back to previous state of "Under Maintenance".
All these happens even if after selecting not to post the incident when the maintenance is available on the settings.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.