Rewind Backups for Jira has moved to Forge, Atlassian's app platform. This article walks existing customers through approving the update in Atlassian Admin, and lists exactly what access Rewind is requesting and why.
What's happening
Rewind Backups for Jira has moved to Forge, Atlassian's app platform. Existing customers need to approve the update once. Atlassian doesn't install it automatically and won't send you a notification. Until it's updated, the app shows as Legacy in Atlassian Admin, with an Update option. Update by November 4, 2026.
Before you begin
- You don't need to log in to Rewind or change anything there.
- Your backups, settings, and backup history stay in place.
- Your backups aren't affected until January 31, 2027. We recommend updating by November 4, 2026 to make sure they continue without interruption.
- New customers can skip this. New installs are already on the latest version.
What you need to do
- Go to Atlassian Admin (admin.atlassian.com) and open Connected apps for your Jira site.
-
Find Rewind Backups for Jira. It will be labeled Legacy and show an Update option.
- Click View app details.
-
Click Update in the top-right corner.
-
A window opens listing the access Rewind is requesting. Review it, then click Accept & Update to confirm.
To check, open View app details again — once the Legacy label and Update option are gone, you're on the latest version.
What Rewind will have access to
Rewind needs this access to back up and restore your Jira data. This is the same data Rewind protects today — Forge only breaks it into more specific categories.
| What it covers | Permissions |
|---|---|
| App runtime and Rewind's app data | read:app-system-token, storage:app, read:app-data:jira |
| Issues and work items | read:jira-work, write:jira-work |
| Users and email addresses (to restore assignees, reporters, and authorship) | read:jira-user, read:email-address:jira |
| Projects and site configuration | read:project:jira, manage:jira-project, manage:jira-configuration |
| Boards and sprints | read:board-scope:jira-software, read:board-scope.admin:jira-software, write:board-scope:jira-software, read:sprint:jira-software, write:sprint:jira-software |
| Jira Service Management requests and customers | read:servicedesk-request, manage:servicedesk-customer |
| Assets (objects, object types, attributes, schemas, configuration) | read:cmdb-object:jira, read:cmdb-type:jira, read:cmdb-attribute:jira, read:cmdb-schema:jira, read:cmdb-config:jira, read:cmdb-icon:jira, write:cmdb-object:jira, write:cmdb-type:jira, write:cmdb-attribute:jira, write:cmdb-schema:jira, write:cmdb-config:jira |
Limitations
- You have to approve this manually. Atlassian doesn't apply it automatically or send a notification. In Atlassian Admin, you'll only see the Legacy label and Update option on the app in Connected apps.
- Only an organization admin can approve it. Other users can't apply the update.
- Backups aren't affected until January 31, 2027, but we recommend updating by November 4, 2026 to make sure they continue without interruption. After that date, backups for apps that haven't updated may be affected.
- Using both apps? Rewind Backups for Confluence and Rewind Backups for Jira are updated separately. If you use both, approve each one. See How to approve the Forge update for Rewind Backups for Confluence.
Related articles
- Rewind app updates for Confluence and Jira — Tracks the full Forge migration for both Confluence and Jira.
- How to approve the Forge update for Rewind Backups for Confluence — For customers who also use Rewind Backups for Confluence.
Need help?
If you have questions or need assistance, contact help@rewind.com or submit a request.