Revyz Command Center for Jira
Revyz Command Center for Jira
Breadcrumbs

Tempo Timesheet Backup & Restore Permissions

About this Page

To provide comprehensive backup and restoration of your Tempo worklogs, the Revyz Token Owner must be granted specific Global Permissions within Jira and Tempo. Relying on project-level permissions is inconsistent and often leads to partial backups or failed restorations.

To provide comprehensive backup and restoration of your Tempo worklogs, the Revyz Token Owner must be granted specific Global Permissions within Jira and Tempo. Relying on project-level permissions is inconsistent and often leads to partial backups or failed restorations.

1. Prerequisites

  • Tempo App: Must be installed on your Jira instance.

  • API Configuration: A Tempo API token must be configured within Revyz.


2. Configuration Steps

Step I: Assign Tempo Administrator Group

  • Navigate to Jira Settings > System > Global Permissions.

  • Locate the Tempo Administrator permission.

  • Add the Token Owner to this group.


  • image-20260430-082306.png

3. Create a Global Permission Role

This step ensures Revyz can access and write worklogs even in restricted projects.

  • Navigate to Apps > Tempo > Settings > Permission Roles.

  • Create a new role (e.g., "Revyz App Role") and assign the Token Owner to it.

  • Set the Access Level to Full Access (Global) and enable:

  • View All Worklogs: Required for full backup coverage.

    Manage Worklogs: Required for successful restoration.

image-20260430-075253.png


4. Enable Override Mode

Ensure Override Mode is enabled on the destination site before attempting a restoration.

image-20260430-080425.png


To ensure 100% data protection for your Tempo worklogs, the Token Owner must have Global Permissions. Relying on project-level settings is inconsistent and often leads to data loss during backups or failures during restoration.

FAQs

Why are Global Permissions required instead of project-level access?

Project-level permissions create gaps in your data protection. If the Token Owner only has local access, Revyz is restricted by the specific rules of each individual project. Global Permissions act as a "Super Permission," allowing Revyz to override local restrictions and ensure every worklog across the entire instance is captured.

What is the risk of using "Project-Level Only" permissions for backups?

If the Token Owner lacks "View All Worklogs" at the global level, Revyz can only back up worklogs created by the Token Owner themselves in restricted projects. All other user data in those projects will be excluded from the backup and lost forever if deleted.

Why does restoration require the "Manage Worklogs" global role?

Restoring data requires Revyz to recreate entries on behalf of other users and set billable hours. These actions are frequently blocked by local project permission schemes. The "Manage Worklogs" global role serves as a master override, ensuring a 100% reliable restoration success rate.

What is "Override Mode" and when should it be used?

Override Mode is a setting that must be enabled on the destination site before starting a restoration. This ensures that Revyz can successfully write worklog data across any project and on behalf of any user by bypassing standard local restrictions.