Uploaded image for project: 'Statuspage'
  1. Statuspage
  2. STATUS-783

Exporting large number of users in audience specific statuspage fails

    • 1
    • Severity 3 - Minor

      Issue Summary

      This is reproducible on Data Center: yes

      When a large number of users is exported, the export fails to generate

      Steps to Reproduce

      1. Open an Audience specific page with at least 11500 users
      2. Go to Audience >> select "Options" >> Export all users

      Expected Results

      All users are successfully exported

      Actual Results

      The export gets 'stuck' and though it initially says it's complete, the download is never made available. Upon revisiting the page later, it says "Your export is taking longer than expected, but it’s still in progress. Return to this page later to see when your export is complete." but it is never completed. 

      Workaround

      Use the API to export the users

            [STATUS-783] Exporting large number of users in audience specific statuspage fails

            Dylan made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Dylan made changes -
            Labels New: cll-tf3202505

            Dylan added a comment -
            Atlassian Update - May 13, 2025

            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

            Dylan added a comment - Atlassian Update - May 13, 2025 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
            Raj Sahu made changes -
            Development Effort New: M [ 13032 ]
            Preventable by New: Load testing [ 19134 ]
            Was this caused by a recent change? New: No [ 19032 ]
            Priority Original: Medium [ 3 ] New: Low [ 4 ]
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            John M made changes -
            Component/s Original: Settings - Users - Other [ 68698 ]
            Component/s New: Page Type - Audience Specific - Users [ 66244 ]
            Key Original: OPSGENIE-2054 New: STATUS-783
            Symptom Severity Original: Severity 3 - Minor [ 18032 ] New: Severity 3 - Minor [ 15832 ]
            Project Original: Opsgenie [ 21710 ] New: Statuspage [ 22011 ]
            John M made changes -
            Summary Original: Exporting users in statuspage fails New: Exporting large number of users in audience specific statuspage fails
            John M made changes -
            Attachment New: 2024-04-19_11-53-57.png [ 455974 ]
            John M created issue -

              Unassigned Unassigned
              a3e616cd17e8 John M
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: