When upgrading your Tempo products, there is no specific order to follow. You just need to make sure that the products you're installing are all in a version compatible with each other and with the JIRA version you're using.
Important before you upgrade Tempo Timesheets from version 7.x.x to 8.x.x
The installation of Tempo Timesheets takes longer than usual because of data migration so you might want to upgrade outside of office hours.
Data might be lost if you downgrade to an earlier version after you upgrade Tempo Timesheets from version 7.x.x to version 8.x.x or later.
Upgrade all Tempo products to compatible versions between themselves before start using them. You can check their compatibility with each other and Jira below.
Tempo for server compatibility
Tempo is compliant with Atlassian’s End of life policy (EOL). Please refer to the following page to learn more about the Atlassian Support End of Life Policy.Atlassian supports feature versions for two years after their release. Tempo products for Jira are also supported for two years (e.g. we support Tempo Timesheets 8.0.x for 2 years after Tempo Timesheets 8.0 was released).Tempo does not provide support for instances on versions that have reached End of Life. The only exception is for assistance related to upgrading from our EOL version to a supported version. All of our products are guaranteed to be compatible with other versions released at the same time. Other versions of our products may still be compatible, but we cannot guarantee this.For the best experience and maximum compatibility, update all of your software to the latest versions of Jira and Tempo.Jira Service DeskIn case you are using only Jira Service Desk, you can see which Jira Core and Software versions are compatible with it here. Please use this information to select the compatible Tempo version.This table shows the compatibility between versions of Jira, Tempo Timesheets for Data Center, Planner, and Budgets.Color LegendOfficially Supported (until Jira version is EOL)Maintenance Supported*Officially Not Supported*Maintenance Supported: We provide technical support for these versions, we also provide fixes for selected Critical and Severe bugs. New features are generally available in the most recent versions only.Timesheets, Planner, BudgetsJira VersionEOL Date8.20-8.229.0-9.89.9-9.129.139.149.1510.0x - 10.4x10.5.x11.018.9.0March 202618.8.0March 202618.7.0March 202618.6.0March 202618.5.0March 202618.4.0March 202618.3.0March 202618.2.0-jira-10March 202618.2.0-jira-9March 202618.1.0-jira-10March 202618.1.0-jira-9March 202618.0.0-jira-10March 202618.0.0-jira-9March 202617.9.2-jira-10March 202617.9.2-jira-9March 202617.9.1-jira-10March 202617.9.1-jira-9March 202617.9.0-jira-10March 202617.9.0-jira-9March 202617.8.1-jira-10March 202617.8.1-jira-9March 202617.8.0March 202617.7.0March 202617.6.0March 202617.5.0March 202617.4.2March 202617.4.1March 202617.4.0March 202617.3.2March 202617.3.1March 202617.3.0Dec 202517.2.0Dec 202517.1.0Dec 202517.0.1Dec 202517.0.0Dec 202516.10.0Nov 202516.9.0Sept 202516.8.2Aug 202516.8.1Aug 202516.8.0Aug 2025
Upgrading to any version
Get information about how your instance is affected by an upgrade, by reading the relevant pages in this chapter.
If you plan on upgrading your JIRA instance, please, upgrade first JIRA and then the Tempo products.
Depending on the upgrade, user permissions might change, features might be removed, or extra upgrade administration tasks might be required.
If you skip one or more versions during the upgrade, make sure to also read the pages for all versions in between your old version and the upgrade version.
If no extra upgrade actions are required for a version, no page exists in this chapter for that version.
We suggest that you start by upgrading the Tempo product you use the most and then proceed to upgrading the other ones.
