Log inSkip to main contentSkip to sidebar
Something went wrong, please try again.
Create and track feature requests for Atlassian products.
  • More
    DashboardsProjectsIssues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

Open issues

  • All issues
  • Open issues
  • Done issues
  • Viewed recently
  • Created recently
  • Resolved recently
  • Updated recently
View all issues and filters
Order by Priority
  1. Bug
    STATUS-991Statuspage signup process Errors
  2. Bug
    STATUS-964IP has been flagged as a scanner for Jira Service Management and Statuspage
  3. Bug
    STATUS-949Select only combobox is inaccessible for screen reader users
  4. Bug
    STATUS-970Incident : Heading not defined
  5. Bug
    STATUS-980Incident : ARIA parent role is not defined for the controls under the ‘Package installation’ section
  6. Bug
    STATUS-921Incidents : Insufficient color contrast for standard text
  7. Bug
    STATUS-920Subscriber : Insufficient color contrast ratio observed for input fields border
  8. Bug
    STATUS-977Component descriptions in the Statuspage component timeline UI are not correctly rendering HTML character entities
  9. Bug
    STATUS-861Email Validation for Subscriber Email Addresses in Audience Specific Pages is more restrictive than the RFC
  10. Bug
    STATUS-955Browser Resize/Refresh Causes Data Loss During Incident Editing
  11. Bug
    STATUS-822Using q= parameter on an API search with any special character shows no results
  12. Bug
    STATUS-943Republic of Korea based SMS Subscribers may receive a their "verify subscription link" split into two messages.
  13. Bug
    STATUS-888The PagerDuty integration can raise duplicate issues when many pagerduty integrations exist in the same Statuspage Organization
  14. Bug
    STATUS-890Creating more than 50 maintenance, results in an incorrect display
  15. Bug
    STATUS-655Implementing Custom Code on Audience Specific Pages Fails
  16. Bug
    STATUS-757Adding more than 10 components in Pagerduty app causes failure to save
  17. Bug
    STATUS-633Update API docs to add flag to update Twitter to incident updates
  18. Bug
    STATUS-373EOL of the New Relic Channel Notifications, which affects Email Automation Parsing
  19. Bug
    STATUS-465Support users incorrectly taking up SP licenses
  20. Bug
    STATUS-694Webhook Notification subscription.
  21. Bug
    STATUS-685While setting up SSO for Audience Specific page with Azure SSO we are getting an error
  22. Bug
    STATUS-550Subscribe to Notification checkbox does not show up 1 certain situation on Audience-Specific Page
  23. Bug
    STATUS-697Using update subscribers API in page access users removes the "Email component subscription" field in export CSV
  24. 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
  25. 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
  26. Bug
    STATUS-515Notification Email Address Exceeds SMTP Character Limit
  27. Bug
    STATUS-639Incomplete HTML Tag Crashes Statuspage
  28. Bug
    STATUS-510Email incident notification sent with the wrong Incident message
  29. Bug
    STATUS-432Issue reaching the Manage your subscription page with an already subscribed number
  30. Bug
    STATUS-939Page type changes in Statuspage Orgs with mutliple pages and the legacy billing engine will receive a GraphQL error
  31. Bug
    STATUS-995Signing up for a Statuspage starts it as a Public Free plan instead of a trial
  32. Bug
    STATUS-994The onboarding process for Statuspage gets stuck when naming the page
  33. Bug
    STATUS-727Generic / Invalid error on Statuspage DNS for DKIM validation issues
  34. Bug
    STATUS-972Clicking "upload logo" button during quick-setup of a new page doesn't work
  35. Bug
    STATUS-992Unable to manage SMS subscription after the initial subscription.
  36. Bug
    STATUS-989Selecting Mexico City timezone results in an incorrect timezone for the page
  37. Bug
    STATUS-415Make Statuspage WCAG 2.1 AA compliant
  38. Bug
    STATUS-670When Statuspage for Jira Service Desk loads in JSM Customer Portal, abnormal behavior occurs
  39. Bug
    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."
  40. Bug
    STATUS-745Clicking on the Metadata XML link in the SAML config results in an error
  41. Bug
    STATUS-983Creating or updating a Page Access Group allows for repeating users
  42. Bug
    STATUS-801Audience Specific pages with 1000+ components intermittently time out during page generation
  43. Bug
    STATUS-957Notifications are not being delivered via Webhook Subscription to MS Teams Channel
  44. Bug
    STATUS-940Selected Tab Not Properly Visible in High Contrast Desert Mode
  45. Bug
    STATUS-941On applying the high contrast Night Sky theme, NPM Logo is not visible
  46. Bug
    STATUS-981Update a component group does not update the "description" element
  47. Bug
    STATUS-907The Status Embed page shows that status embed is offline despite it working properly
  48. Bug
    STATUS-960Email notifications truncate long component names, even though the component management page does not show or enforce a maximum length limit
  49. Bug
    STATUS-662On Audience Specific pages, ""only_show_if_degraded": true" option is not respected
  50. Bug
    STATUS-969Webhook Payload Missing "Manage Subscription" Link
Refresh results
1 2 3 4Next >>
18 of 157
Uploaded image for project: 'Statuspage'
  1. Statuspage
  2. STATUS-373

EOL of the New Relic Channel Notifications, which affects Email Automation Parsing

Log In
Short Term Backlog
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • Components - Automation
    • None
    • 9
    • Severity 2 - Major

      Issue Summary

      By end of first half of 2023, the New Relic Channel Notifications with be set to EOL and will be replaced by the workflows process: https://docs.newrelic.com/docs/alerts-applied-intelligence/transition-guide

      Workflows: https://docs.newrelic.com/docs/alerts-applied-intelligence/applied-intelligence/incident-workflows/incident-workflows/

      This will break the New Relic email automation parsing that we do to change component statuses as the new workflows functionality does not parse. This would also mean that a document change would need to happen as well: https://support.atlassian.com/statuspage/docs/set-up-new-relic-alerts-parsing/

      It appears to use a concept of "destinations": https://docs.newrelic.com/docs/alerts-applied-intelligence/notifications/destinations/ instead of these channel notifications.

      Things I noticed:

      Notification channels send an email to the component automation address with "Incident Opened" or "Incident Closed" and they are sent from "alert@newrelic.com"

      Workflows send notifications from "noreply@notifications.newrelic.com" and the subject line includes "critical priority issue is active"

      The expectation would be that once depreciated, customers can use the new workflows feature in New Relic and still have the component automations work.

      Workaround

      This template is expected to work for customers as a workaround:

      {{ issueTitle }}, component is {{eq "CLOSED" status yes='CLOSED' no='failing'}}   

      NR allows for the email notification subject to be customized and this should be applied in the workflow setup: 

            • Sort By Name
            • Sort By Date
            • Ascending
            • Descending
            • Thumbnails
            • List
        1. image-2022-10-06-16-54-21-490.png
          image-2022-10-06-16-54-21-490.png
          38 kB
          06/Oct/2022 8:54 PM

        mentioned in

        Page Loading...

        relates to

        STSPG-10863 Loading...

              • All
              • Comments
              • Work Log
              • History
              • Activity

                Unassigned Unassigned
                jklein@atlassian.com Jesse Klein
                Affected customers:
                0 This affects my team
                Watchers:
                6 Start watching this issue

                  Created:
                  15/Jun/2022 9:47 PM
                  Updated:
                  07/Mar/2024 9:48 AM
                  • Atlassian Jira Project Management Software
                  • About Jira
                  • Report a problem
                  • Privacy policy
                  • Notice at Collection

                  Atlassian