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.
StatuspageProject Type: software

Statuspage

  • Issues
  • Reports
  • Components

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-949Select only combobox is inaccessible for screen reader users
  3. Bug
    STATUS-970Incident : Heading not defined
  4. Bug
    STATUS-980Incident : ARIA parent role is not defined for the controls under the ‘Package installation’ section
  5. Bug
    STATUS-999On Audience Specific Pages, having more than 150 groups assigned to a User in Azure causes an SSO login failure
  6. Bug
    STATUS-997Some AWS third-party components are falsely showing as "Degraded"
  7. Bug
    STATUS-685While setting up SSO for Audience Specific page with Azure SSO we are getting an error
  8. Bug
    STATUS-921Incidents : Insufficient color contrast for standard text
  9. Bug
    STATUS-920Subscriber : Insufficient color contrast ratio observed for input fields border
  10. Bug
    STATUS-977Component descriptions in the Statuspage component timeline UI are not correctly rendering HTML character entities
  11. Bug
    STATUS-861Email Validation for Subscriber Email Addresses in Audience Specific Pages is more restrictive than the RFC
  12. Bug
    STATUS-955Browser Resize/Refresh Causes Data Loss During Incident Editing
  13. Bug
    STATUS-822Using q= parameter on an API search with any special character shows no results
  14. Bug
    STATUS-943Republic of Korea based SMS Subscribers may receive a their "verify subscription link" split into two messages.
  15. Bug
    STATUS-888The PagerDuty integration can raise duplicate issues when many pagerduty integrations exist in the same Statuspage Organization
  16. Bug
    STATUS-890Creating more than 50 maintenance, results in an incorrect display
  17. Bug
    STATUS-655Implementing Custom Code on Audience Specific Pages Fails
  18. Bug
    STATUS-757Adding more than 10 components in Pagerduty app causes failure to save
  19. Bug
    STATUS-633Update API docs to add flag to update Twitter to incident updates
  20. Bug
    STATUS-373EOL of the New Relic Channel Notifications, which affects Email Automation Parsing
  21. Bug
    STATUS-465Support users incorrectly taking up SP licenses
  22. Bug
    STATUS-694Webhook Notification subscription.
  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-1006SMS notifications sent to the Republic of Ireland users are marked as 'Likely Scam'
  31. Bug
    STATUS-1000Connecting a Statuspage Page to a JSM project via "Statuspage Add-on" in JSM fails
  32. Bug
    STATUS-1001Cannot update StatusPage from Jira iOS App
  33. Bug
    STATUS-636Wrong graph on Metric by Datadog
  34. Bug
    STATUS-741Statuspage integration with JSM Portal - Brief blank space flashes at the top of the portal view
  35. Bug
    STATUS-994The onboarding process for Statuspage gets stuck when naming the page
  36. Bug
    STATUS-995Signing up for a Statuspage starts it as a Public Free plan instead of a trial
  37. Bug
    STATUS-996Customers with a custom email addresses that use Proofpoint in the SPF record will have it intermittently marked invalid
  38. Bug
    STATUS-432Issue reaching the Manage your subscription page with an already subscribed number
  39. Bug
    STATUS-972Clicking "upload logo" button during quick-setup of a new page doesn't work
  40. Bug
    STATUS-992Unable to manage SMS subscription after the initial subscription.
  41. Bug
    STATUS-989Selecting Mexico City timezone results in an incorrect timezone for the page
  42. Bug
    STATUS-415Make Statuspage WCAG 2.1 AA compliant
  43. Bug
    STATUS-670When Statuspage for Jira Service Desk loads in JSM Customer Portal, abnormal behavior occurs
  44. 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."
  45. Bug
    STATUS-745Clicking on the Metadata XML link in the SAML config results in an error
  46. Bug
    STATUS-983Creating or updating a Page Access Group allows for repeating users
  47. Bug
    STATUS-801Audience Specific pages with 1000+ components intermittently time out during page generation
  48. Bug
    STATUS-957Notifications are not being delivered via Webhook Subscription to MS Teams Channel
  49. Bug
    STATUS-940Selected Tab Not Properly Visible in High Contrast Desert Mode
  50. Bug
    STATUS-941On applying the high contrast Night Sky theme, NPM Logo is not visible
Refresh results
1 2 3 4Next >>
1 of 160
Uploaded image for project: 'Statuspage'
  1. Statuspage
  2. STATUS-991

Statuspage signup process Errors

Log In
Short Term Backlog
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Highest Highest
    • Product - Errors / Performance
    • None
    • Severity 1 - Critical

      Issue Summary

      When signing up for a new Statuspage, a customer goes through the initial setup onboarding to start their page. This should start them on a Public Trial. Instead, the customer can't complete the onboarding process. Furthermore, the page activates as a Public Free plan instead of a Public Trial, which prevents the user from exploring other page types.

      Steps to Reproduce

      Quick Setup Broken:

      1. Go to https://www.atlassian.com/try/cloud/signup?bundle=statuspage
      2. Create a new Atlassian site
      3. After waiting for the site creation to be completed, you're presented with a screen to enter your page name.
      4. Enter a page name and click continue.
      5. The page reloads to the same screen.
      6. Re-enter your page name and click continue.
      7. An error appears: "Organization does not need name set"
      8. Go to your URL and remove "/quick-setup/name"
      9. This successfully leads you to your Statuspage

      Free Plan instead of Trial:

      1. Once you're at your page, go to "your page" > page type.
      2. This page shows that the page is active and on a Free plan instead of the Trial plan

      Expected Results

      The setup onboarding should not reload the page to enter a name and should progress forward. It should not throw an error for naming the page.

      The Page should not activate as a Free plan and should start as a free trial, allowing the user to change page types.

      Actual Results

      The setup onboarding gets stuck on the name creation.

      The page starts as an activated Free plan instead of a Trial.

      Workaround

      To get through the onboarding error, you need to remove "/quick-setup/name" from the URL.

      If you are an affected customer on a Free plan, you can open a billing ticket and they can revert your plan back to a trial.

            • All
            • Comments
            • Work Log
            • History
            • Activity
            There are no comments yet on this issue.

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

                Created:
                03/Jun/2025 8:55 PM
                Updated:
                19/Jun/2025 3:19 AM
                • Atlassian Jira Project Management Software
                • About Jira
                • Report a problem
                • Privacy policy
                • Notice at Collection

                Atlassian