Org admin cannot schedule backups using the Backup and Restore Tool due to a "Something went wrong" error

XMLWordPrintable

    • 1

      Issue Summary

      When an organization admin attempts to use the backup policy management tool at Manage Backup Policies, they receive a generic "Something went wrong" error when trying to edit the schedule settings.

      Steps to Reproduce

      1. Go to admin.atlassian.com. Select your organization if you have more than one.
      2. Select Settings > Backup and restore.
      3. Select Create new policy.
      4. In the Policy name field, enter a name for the policy.
      5. Select the app.
      6. Include or exclude entities as needed.
      7. Select Set schedule.
      8. From the Frequency dropdown list:
        1. Select One-time if you want to run the backup once.
        2. Select Daily or Weekly if you want to run the backup in a daily or weekly schedule.
      9. Select the date when you want to run the backup. The backup date and time will load.
      10. Select Set Schedule.

      Expected Results

      The backup should be scheduled successfully without requiring additional permissions beyond organization admin rights.

      Actual Results

      Users encounter a "Something went wrong" error, and a 403 Forbidden error is logged in the developer tools. The error message indicates that the current user is not permitted to use Confluence or Jira, and scheduling the backup fails.

      The following exception is thrown in the dev tools:

      {
      [...]
        "status": 500,
        "message": "403 Forbidden from GET http://atlassian-proxy.
      [...]"
      }
      

      Workaround

      Currently, the workaround is to ensure that the org admin scheduling the backup has both organization admin and product admin permissions. 

      Suggested Solution

      Update the backup policy management tool to allow organization admins to schedule backups without requiring additional product admin permissions. Additionally, improve error messaging to provide more specific guidance on permission requirements if a user lacks necessary access.

            Assignee:
            Unassigned
            Reporter:
            Karinna C. [Atlassian Support]
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: