Open issues

Order by Priority
  1. Bug
    STATUS-956The Slack Third Party Component does not reflect what Slack is showing
  2. Bug
    STATUS-949Select only combobox is inaccessible for screen reader users
  3. Bug
    STATUS-934Tooltip inaccessible for both keyboard only and screen reader users
  4. Bug
    STATUS-929Home page : Missing heading semantics
  5. Bug
    STATUS-861Email Validation for Subscriber Email Addresses in Audience Specific Pages is more restrictive than the RFC
  6. Bug
    STATUS-955Browser Resize/Refresh Causes Data Loss During Incident Editing
  7. Bug
    STATUS-920Subscriber : Insufficient color contrast ratio observed for input fields border
  8. Bug
    STATUS-921Incidents : Insufficient color contrast for standard text
  9. Bug
    STATUS-822Using q= parameter on an API search with any special character shows no results
  10. Bug
    STATUS-943Republic of Korea based SMS Subscribers may receive a their "verify subscription link" split into two messages.
  11. Bug
    STATUS-790Unable to completely remove Statuspage product from CCP Atlassian site
  12. Bug
    STATUS-888The PagerDuty integration can raise duplicate issues when many pagerduty integrations exist in the same Statuspage Organization
  13. Bug
    STATUS-890Creating more than 50 maintenance, results in an incorrect display
  14. Bug
    STATUS-655Implementing Custom Code on Audience Specific Pages Fails
  15. Bug
    STATUS-870RSS Feeds fail validation and throw errors
  16. Bug
    STATUS-833Statuspage logs out automatically when manage portal & statuspage are browsed together
  17. Bug
    STATUS-757Adding more than 10 components in Pagerduty app causes failure to save
  18. Bug
    STATUS-633Update API docs to add flag to update Twitter to incident updates
  19. Bug
    STATUS-373EOL of the New Relic Channel Notifications, which affects Email Automation Parsing
  20. Bug
    STATUS-465Support users incorrectly taking up SP licenses
  21. Bug
    STATUS-694Webhook Notification subscription.
  22. Bug
    STATUS-685While setting up SSO for Audience Specific page with Azure SSO we are getting an error
  23. Bug
    STATUS-550Subscribe to Notification checkbox does not show up 1 certain situation on Audience-Specific Page
  24. Bug
    STATUS-697Using update subscribers API in page access users removes the "Email component subscription" field in export CSV
  25. Bug
    STATUS-603Marketplace application Statuspage for Jira Service Management configuration page fails to load when site has a large number of Jira Service Management projects
  26. Bug
    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
  27. Bug
    STATUS-515Notification Email Address Exceeds SMTP Character Limit
  28. Bug
    STATUS-639Incomplete HTML Tag Crashes Statuspage
  29. Bug
    STATUS-510Email incident notification sent with the wrong Incident message
  30. Bug
    STATUS-961Unsubscribe modal doesn't use body background color
  31. Bug
    STATUS-962Incident : Information on the page is coded via CSS pseudo elements.
  32. Bug
    STATUS-941On applying the high contrast Night Sky theme, NPM Logo is not visible
  33. Bug
    STATUS-940Selected Tab Not Properly Visible in High Contrast Desert Mode
  34. Bug
    STATUS-960Email notifications truncate long component names, even though the component management page does not show or enforce a maximum length limit
  35. Bug
    STATUS-636Wrong graph on Metric by Datadog
  36. Bug
    STATUS-957Notifications are not being delivered via Webhook Subscription to MS Teams Channel
  37. Bug
    STATUS-864Status API does not work externally for Audience Specific pages, even when using an API key
  38. Bug
    STATUS-950Functionality missing from PagerDuty App
  39. Bug
    STATUS-859Users with the product admin role cannot add new pages
  40. Bug
    STATUS-670When Statuspage for Jira Service Desk loads in JSM Customer Portal, abnormal behavior occurs
  41. Bug
    STATUS-741Statuspage integration with JSM Portal - Brief blank space flashes at the top of the portal view
  42. Bug
    STATUS-841Incident Creation Page on Statuspage Fails to Load Due to Excessive Incident Templates
  43. Bug
    STATUS-609Updating an incident creation to a later date/time via the UI does not update the "created_at" attribute
  44. Bug
    STATUS-945Creating a component via API on an Audience-specific page does not respect the only_show_if_degraded flag
  45. Bug
    STATUS-923GitHub Component Shift to Degraded State Without Performance Impact on Third-Party Component
  46. Bug
    STATUS-924Uploading .gif file for page favicon hangs
  47. Bug
    STATUS-281"Subscribe to updates" string is hard coded and cannot be localized
  48. Bug
    STATUS-939Page type changes in Statuspage Orgs with mutliple pages and the legacy billing engine will receive a GraphQL error
  49. Bug
    STATUS-707Vulnerable open source JS library - HIGHCHARTS
  50. Bug
    STATUS-415Make Statuspage WCAG 2.1 AA compliant
Refresh results
1 of 163
Uploaded image for project: 'Statuspage'
  1. Statuspage
  2. STATUS-956

The Slack Third Party Component does not reflect what Slack is showing

    • 5
    • Severity 2 - Major

      Issue Summary

      Slack is a third party component within Statuspage. When Slack shared a recent outage, it was not reflected for third-party components.

      Steps to Reproduce

      1. Enable Slack as a third party component.
      2. Wait for Slack to post component outages
      3. Components should be shown on your page but they are not actually changing.

      Expected Results

      When Slack's outage occurred, the Messaging and Apps components on the Statuspage pages that use Slack as a third-party component should have changed to match Slack.

      Actual Results

      No changes to the Statuspage pages occurred during Slack's component outages.

      Workaround

      Slack's status page is available for viewing. It's recommended to subscribe to their RSS feed. It is also possible to manually update the third-party component to match Slack's using the override button while editing the component.

            There are no comments yet on this issue.

              Unassigned Unassigned
              jklein@atlassian.com Jesse Klein
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: