-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Severity 3 - Minor
Issue Summary
When maintenance is scheduled in Statuspage the NEWLY CREATED Statuspage components are generating "Statuspage: Long-running degraded component" emails to Statuspage users.
This is reproducible on Data Center: (yes) / (no)
Yes
Steps to Reproduce
- Create new components
- Schedule Maintenance including these newly created components.
- When the scheduled maintenance duration is longer than 3 hours, the previously created OLD components do not generate any email but newly created COMPONENTS generate "Statuspage: Long-running degraded component" emails for 3 hours 6 hours 12 hours etc...
- This issue is not repeated when the same components are set to maintenance next time.
- Also, it is difficult to confirm as to how long it will take for the new components to have this issue. Was able to replicate for newly created components on the same day and one of the customer experienced the issue for 4 days older component.
Expected Results
Since the components are set to under maintenance using the scheduled maintenance option "Statuspage: Long-running degraded component" emails are not expected to the account users.
Actual Results
Users are getting "Statuspage: Long-running degraded component" for newly created components only.
Workaround
Currently, there is no known workaround for this behaviour. A workaround will be added here when available. However, the issue is only visible on the new components and that too for the first maintenance scheduled. It is not reproducible for the next maintenance scheduled.
[STATUS-770] Long-running degraded component notifications for Under Maintenance components
Resolution | New: Timed out [ 10 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Labels | New: cll-tf3202505 |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Support reference count | New: 1 |
Hi everyone,
Thank you for raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be prioritised. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all cloud users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know by commenting back on this issue.
Thank you again for providing valuable feedback to our team, we appreciate your engagement and partnership in helping improve our products.
Atlassian Cloud Engineering