- STATUS-991Statuspage signup process Errors
- STATUS-949Select only combobox is inaccessible for screen reader users
- STATUS-970Incident : Heading not defined
- STATUS-980Incident : ARIA parent role is not defined for the controls under the ‘Package installation’ section
- STATUS-999On Audience Specific Pages, having more than 150 groups assigned to a User in Azure causes an SSO login failure
- STATUS-997Some AWS third-party components are falsely showing as "Degraded"
- STATUS-685While setting up SSO for Audience Specific page with Azure SSO we are getting an error
- STATUS-921Incidents : Insufficient color contrast for standard text
- STATUS-920Subscriber : Insufficient color contrast ratio observed for input fields border
- STATUS-977Component descriptions in the Statuspage component timeline UI are not correctly rendering HTML character entities
- STATUS-861Email Validation for Subscriber Email Addresses in Audience Specific Pages is more restrictive than the RFC
- STATUS-955Browser Resize/Refresh Causes Data Loss During Incident Editing
- STATUS-822Using q= parameter on an API search with any special character shows no results
- STATUS-943Republic of Korea based SMS Subscribers may receive a their "verify subscription link" split into two messages.
- STATUS-888The PagerDuty integration can raise duplicate issues when many pagerduty integrations exist in the same Statuspage Organization
- STATUS-890Creating more than 50 maintenance, results in an incorrect display
- STATUS-655Implementing Custom Code on Audience Specific Pages Fails
- STATUS-757Adding more than 10 components in Pagerduty app causes failure to save
- STATUS-633Update API docs to add flag to update Twitter to incident updates
- STATUS-373EOL of the New Relic Channel Notifications, which affects Email Automation Parsing
- STATUS-465Support users incorrectly taking up SP licenses
- STATUS-694Webhook Notification subscription.
- STATUS-550Subscribe to Notification checkbox does not show up 1 certain situation on Audience-Specific Page
- STATUS-697Using update subscribers API in page access users removes the "Email component subscription" field in export CSV
- STATUS-603Marketplace application Statuspage for Jira Service Management configuration page fails to load when site has a large number of Jira Service Management projects
- STATUS-565The Metric ID showing on the Advanced Options page of a custom System Metrics does not align with the response of the "Get a list of metrics" API and cannot be used for "Add data to a metric" API request
- STATUS-515Notification Email Address Exceeds SMTP Character Limit
- STATUS-639Incomplete HTML Tag Crashes Statuspage
- STATUS-510Email incident notification sent with the wrong Incident message
- STATUS-1013New API Keys don't work on the Status API for Private pages.
- STATUS-996Customers with a custom email addresses that use Proofpoint in the SPF record will have it intermittently marked invalid
- STATUS-1011If a Component Description covers another component description's "?" icon, the second description wont appear
- STATUS-819Private page are not auto-refreshed
- STATUS-1008Maintenance update incorrectly state no component is affected if component already in maintenance state
- STATUS-1009System Metric ID Changes Upon Data Submission in Statuspage.
- STATUS-1001Cannot update StatusPage from Jira iOS App
- STATUS-1006SMS notifications sent to the Republic of Ireland users are marked as 'Likely Scam'
- STATUS-1000Connecting a Statuspage Page to a JSM project via "Statuspage Add-on" in JSM fails
- STATUS-636Wrong graph on Metric by Datadog
- STATUS-741Statuspage integration with JSM Portal - Brief blank space flashes at the top of the portal view
- STATUS-994The onboarding process for Statuspage gets stuck when naming the page
- STATUS-995Signing up for a Statuspage starts it as a Public Free plan instead of a trial
- STATUS-432Issue reaching the Manage your subscription page with an already subscribed number
- STATUS-972Clicking "upload logo" button during quick-setup of a new page doesn't work
- STATUS-992Unable to manage SMS subscription after the initial subscription.
- STATUS-989Selecting Mexico City timezone results in an incorrect timezone for the page
- STATUS-415Make Statuspage WCAG 2.1 AA compliant
- STATUS-670When Statuspage for Jira Service Desk loads in JSM Customer Portal, abnormal behavior occurs
- STATUS-912If a user is subscribed to any webhooks on StatusPage, then the Create Subscriber API throws an error saying "The email, phone information, or endpoint provided is already subscribed to updates."
- STATUS-745Clicking on the Metadata XML link in the SAML config results in an error
20 of 164