Upgrading Zephyr from Connect to Forge
Atlassian is ending support for Connect apps on January 31, 2027. Zephyr on Connect would likely keep running after that date, but SmartBear cannot guarantee that it will work smoothly and without issues. To make sure Zephyr works as expected with Jira, SmartBear is upgrading Zephyr instances that still run on the Connect framework to the Forge version.
This page explains what to expect during the upgrade and what, if anything, you need to do afterward.
Which customers does this apply to?
Your Zephyr version | What does this mean for you? |
|---|---|
2.x, 3.x, 4.x, 5.x | Your instance runs on Connect and will be upgraded to Forge. This page explains what to expect. |
6 or later | Your instance is already on Forge, and the changes described on this page have already been applied to your app. Nothing here affects you. To get the latest version, a Jira admin can manually update the app. Depending on what the update includes, you may be asked to approve changes. |
How to check your Zephyr version
To check your Zephyr version, do the following:
In Jira, click the cogwheel icon in the top right corner to open Settings.
Click Marketplace apps.
On the Marketplace apps page, click Take me there in the message that says app management has moved to Administration.
In the list of apps installed on your Jira instance, find Zephyr.
Click View app details. The current version is shown with the rest of the app information.
You must be a Jira admin to do this. If you are not a Jira admin, ask your Jira admin to check the version for you.
What to expect
The upgrade is automatic.
SmartBear performs the upgrade for you, so you do not need to install or approve anything. SmartBear upgrades your instance to a Forge version with permissions equivalent to your current version, so no Jira admin approval is needed. The main change is the permission that allows Zephyr to run as a Forge app, which is necessary to keep it working. Although SmartBear upgrades your instance automatically, you can also update the app at any time from Settings rather than waiting for the automatic upgrade. See Upgrade on your own.
You can also upgrade on your own.
If you do not want to wait for SmartBear to upgrade your instance, a Jira admin can update the app at any time. If you are on version 2, 3, 4, or 5, this installs the latest version and you will be asked to approve new permissions.
You will be notified first.
Before your instance is upgraded, you will see a message inside Zephyr telling you the upgrade is coming.
Upgrades happen in stages.
SmartBear upgrades instances gradually rather than all at once, so the exact date may vary by customer. The in-app message is your notice that your upgrade is next.
You will be on Forge, but not necessarily the latest version.
The automatic upgrade moves your instance from Connect to Forge. It does not move you to the latest version of Zephyr because updating from Connect to the latest version adds permissions that need a Jira admin's approval. You can update to the latest version later, whenever you choose.
There is no downtime.
The upgrade does not take Zephyr offline, so your team can keep working as usual while the upgrade is underway.
The upgrade is required.
Because Connect reaches the end of support on January 31, 2027, SmartBear cannot guarantee that Zephyr will work as expected on Connect after that date. To keep your instance reliable, all Connect instances need to move to Forge.
Your data is safe
The upgrade does not affect your test cases, test executions, test cycles, or test plans. Traceability links between Jira work items and Zephyr continue to work as before.
What changes after the upgrade
The change below only affect customers upgrading from Zephyr versions 2, 3, 4, or 5. If you are on version 6 or later, your instance is already on Forge and this change has already been applied to your app.
The API token page moves
If you use the Zephyr REST API, the page where you generate API tokens has moved. For instructions on creating and managing tokens in the new location, see API Access Tokens Management.
Your existing API tokens do not need to be regenerated.
Upgrade on your own
If you would rather not wait for SmartBear to upgrade your instance, a Jira admin can update Zephyr at any time. This takes a few minutes, and there is no downtime.
To upgrade Zephyr on your own, do the following:
In Jira, click the cogwheel icon in the top right corner to open Settings.
Click Marketplace apps.
On the Marketplace apps page, click Take me there in the message that says app management has moved to Administration.
In the list of installed apps, find Zephyr and click View app details.
Click Update app in the top right corner of the page.
If you are prompted to approve changes, review them and click Approve to complete the update.
If you are updating from version 2, 3, 4, or 5, the update installs the latest version of Zephyr, which includes new permissions that you need to approve. See Why does the latest version ask for new permissions?. The change described in What changes applies to your instance as soon as the update finishes. Your data is not affected.
If you are already on version 6 or later, updating to the latest version is a major update that you need to apply manually. Depending on what the update includes, Jira may ask you to review and approve changes. If you are prompted, the approval screen shows exactly what is being requested.
Why does the latest version ask for new permissions?
This section applies to customers updating from versions 2, 3, 4, or 5. Moving from Connect to the latest version of Zephyr adds permissions, so Jira requires an admin to approve them when the update is installed. Zephyr uses its permissions for the following:
Read and write Jira work items and projects. This is how Zephyr links test cases and executions to Jira issues, validates traceability links, builds coverage reports, and respects which projects each user can access.
Read Jira user information. Zephyr stores people as Jira account IDs, so it looks up names and profile details to show them in the interface, in exported reports, and during data import. It also checks whether a user should have access to Zephyr.
Manage project and app settings. When an admin turns Zephyr on or off for a project, or changes which issue types appear in test executions, Zephyr saves those settings in Jira.
Receive Jira event notifications. Zephyr is notified when a project is deleted, updated, or archived, when an issue link is removed, and when a user is deleted or updated, so its data stays consistent.
Authenticate with Jira under Forge. Zephyr uses Forge's system and user tokens so it can make Jira calls on behalf of each user, ensuring people only see test assets in projects they can access.
Work with Rovo. This lets the Zephyr Agent for Rovo read your test cases, cycles, plans, and permissions when you ask about them in Rovo Chat.
Updating after you are on Forge
Once your instance is on Forge, Zephyr updates reach you in one of three ways:
Versionless releases are applied automatically. They deliver fixes and improvements inside the app and do not change the version number.
Minor releases are applied automatically. You may notice a change appear.
Major releases must be applied manually by a Jira admin. Until an admin applies the update, your site stays on the previous version. This is how Atlassian handles major app upgrades in general and cannot be changed.
A major release does not always mean new permissions. Atlassian classifies a release as major or minor based on the kind of change made to the app. For example, a change related to data residency or where the app stores data can also require a major release.
If you are on version 6 or later, updating to the latest version is a major update that you need to apply manually. Depending on the changes in that version, Jira may ask you to approve them. Whatever is requested is shown on the approval screen before you confirm.
To learn more about each type of release, see Understanding Zephyr and Zephyr Essential Releases and Atlassian's documentation on Forge app versions.
Frequently asked questions
Do I need to do anything to prepare?
No.
How do I know which version of Zephyr I am on?
A Jira admin can check it from the Zephyr app details page.
Can I postpone or opt out of the upgrade?
No. Atlassian ends support for Connect on January 31, 2027, and SmartBear cannot guarantee Zephyr will work as expected on Connect after that date. To ensure the best experience, all Connect instances are being moved to Forge.
Will Zephyr be unavailable during the upgrade?
No. There is no downtime, whether SmartBear upgrades your instance or you update it yourself.
Will I lose any data?
No. Your Zephyr data is not affected.
Will anything else change or break?
Your test data, test executions, cycles, plans, and traceability links to Jira work items are not affected. If you are upgrading from version 2, 3, 4, or 5, the API token page will move. Customers on version 6 or later are not affected by this change.
Do I have to approve anything when I update myself?
It depends on the version you are updating from and what the new version includes. If you are on version 2, 3, 4, or 5, you will be asked to approve new permissions. If you are on version 6 or later, the update is a major release that you apply manually, and Jira may ask you to approve changes included in it. Any required approvals are shown on the screen before you confirm. You do not need to approve anything for the automatic upgrade that SmartBear performs.
Why am I asked to approve permissions when I update from version 2, 3, 4, or 5?
Moving from Connect to the latest version adds permissions, and Jira requires an admin to approve any update that adds permissions. When SmartBear upgrades your instance, it moves you to a Forge version with permissions equivalent to Connect, so no approval is needed. The main change is the permission that allows Zephyr to run as a Forge app, which is necessary to keep it working.
If I wait for SmartBear to upgrade my instance, will I be on the latest version?
No. You will be on Forge, which is required before Connect support ends on January 31, 2027. To get the latest version, a Jira admin can update Zephyr manually at any time.
Why do I have to apply updates manually? Can this happen automatically?
Major updates must be applied manually by a Jira admin. This is how Atlassian handles major app upgrades and cannot be changed. Major releases cover many kinds of changes, not only new permissions, so manual approval can be required for several reasons. Minor and versionless releases are applied automatically. See Understanding Zephyr and Zephyr Essential Releases.
I am on version 6 or later. Does any of this affect me?
No. Your instance is already on Forge, and the API token change has already been applied to your app. You can update to the latest version at any time by following the steps in Upgrade on your own. Depending on what the update includes, you may be asked to approve changes.
I am having a different problem after the upgrade. Where do I get help?
Contact SmartBear Support and provide your Jira instance details and a description of what you are seeing.