If the Qase app in your Jira Cloud site does not match the screenshots in our installation guide, you are almost certainly still on the older version of the app. Nothing is broken, and there is nothing you need to do.
Atlassian is retiring Connect, the framework the Qase app was originally built on, and has published a timeline for it. We have rebuilt the app on Atlassian's newer framework, Forge, and that rebuild is complete.
What this means for you
Every new installation is the Forge version. If you install Qase for Jira Test Management from the Atlassian Marketplace today, you get it automatically. There is no separate listing and no version to choose.
Existing installations are migrated for you. Atlassian performs the migration itself, gradually, across all sites that have the app. You do not need to uninstall anything, reconnect anything, or ask us to schedule it. Your links between Jira issues and Qase test cases, your defect status mappings and your project access settings all carry over.
Both versions do the same things. The feature set is identical. What differs is the screen layout, because the two frameworks render their interfaces differently — so some buttons sit in a different place and a few carry different labels.
How to tell which version you have
Open a Jira issue and look at the Qase panels.
What you see | Which version |
Panels named Qase and Linked Qase test runs, with Link a test case and Link a test run buttons | Forge, the current version |
A Qase: Test cases panel with Link a case, and a Qase: Runs module you switch on from the issue options | Connect, the older version |
The Jira Cloud installation guide documents the Forge version.
If something stops working
The migration should be invisible. If the Qase panels on an issue start asking you to connect a workspace after the app has been working, a Jira administrator can reconnect the site — open Apps → Qase for Jira in Jira's administration settings and connect it to your Qase workspace again. Your existing links are kept.
If that does not resolve it, contact us at [email protected] with your Jira site address and your Qase workspace name.