Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-61618

API call to check status of backup jobs and a post to indicate it has completed with or without errors.

XMLWordPrintable

    • 1
    • 3

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Problem Definition

      Backups can often fail for a vareity of reasons. It would be great to have an API call that check the status of a backup job. If a backup job fails users in cloud can either contact support or check the webdav directory after the average time it takes the backup to run.

      Suggested Solution

      As well as have a post that pushes a call back URL to indicate the job completed either with our without errors.

            [JRACLOUD-61618] API call to check status of backup jobs and a post to indicate it has completed with or without errors.

            Charles McLaughlin added a comment -

            Thanks for opening this issue Ramiro.

            The idea here is /rest/obm/1.0/runbackup should return a Job ID. Another API method should be available to check the Job status. Perhaps something like /rest/obm/1.0/status/<JOB_ID>.

            That, in my opinion, is bare minimum functionality. Compare that to the current state - 'runback' returns nothing useful, except if you call it repeatedly you'll get a message that a backup is in progress or that you're throttled for calling it too often. You have to poll the webdav directory waiting for the backup file to show up... and if there's an error, there's no explanation why.

            I'm also suggesting that when calling 'runback', it would be nice to provide a callback URL where customers can be notified that backup jobs are done - upon success or failure we'd be notified. For instance, that could trigger a job to download the backup file... much more efficient than polling.

            Charles McLaughlin added a comment - Thanks for opening this issue Ramiro. The idea here is /rest/obm/1.0/runbackup should return a Job ID. Another API method should be available to check the Job status. Perhaps something like /rest/obm/1.0/status/<JOB_ID>. That, in my opinion, is bare minimum functionality. Compare that to the current state - 'runback' returns nothing useful, except if you call it repeatedly you'll get a message that a backup is in progress or that you're throttled for calling it too often. You have to poll the webdav directory waiting for the backup file to show up... and if there's an error, there's no explanation why. I'm also suggesting that when calling 'runback', it would be nice to provide a callback URL where customers can be notified that backup jobs are done - upon success or failure we'd be notified. For instance, that could trigger a job to download the backup file... much more efficient than polling.

              Unassigned Unassigned
              jcastro Jose Castro (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: