The old app stops working on October 15. Here’s what to do.
If you run QA out of Jira, this affects you. We rebuilt Kualitee’s Jira integration and shipped it as a new app on the Atlassian Marketplace. It’s built on Atlassian Forge now, and it brings all of Kualitee’s test management right inside Jira. It replaces the old app, which stops working on October 15.
Here’s what changed and why. And don’t worry, you won’t lose any data. You just move to the new app.
What The New App Gives You
The old app connected Kualitee to Jira, but most of the real work still lived in a separate tool. You managed test cases in one place and tracked defects in another. Then you spent time lining the two up. That’s usually where visibility slips, especially when a release is close, and everyone wants to know one thing: are we ready to ship?
The new app fixes that. All of Kualitee’s test management now runs inside Jira:
- Full test case management. Create, organize, and run test cases without leaving Jira.
- Traceability. Link tests to Jira issues, so coverage and gaps show up on the board your team already uses.
- Execution tracking. See what’s been tested, what passed, and what’s still open, tied to your sprints and releases.
- Reporting you can act on. Not just activity. Whether the work is actually done.
The idea isn’t more tools. It’s fewer tabs and one clear place to see where quality stands.
Why We Rebuilt It on Forge
There are two reasons. One is about Atlassian. One is about you.
First, Atlassian is ending support for Connect, the framework the old app was built on. Connect apps run on servers outside Atlassian and talk to Jira through APIs. That worked fine for years. But Atlassian is moving everything to Forge, and new features are Forge-only now. Staying on Connect wasn’t really an option.
Second, Forge is a better fit for a test management tool. And the upside is real, not just talk.
- It runs on Atlassian’s own infrastructure. Forge apps run inside Atlassian’s environment instead of on an outside server. Fewer parts sit between Kualitee and your Jira data. That means better speed and fewer things that can break.
- Your admins will clear it faster. Forge keeps data inside Atlassian by default, with tight permissions and data residency support. If you’re in banking or fintech, that can turn a long security review into a short one. Your admin isn’t checking some outside vendor’s servers anymore.
- It feels native. Atlassian runs the backend, so the app behaves like a real part of Jira, not something bolted on.
So this wasn’t a copy and paste to a new framework. We used the move to give you the full product on a stronger base.
What to Do Before October 15
The old app, Kualitee Test Management for Jira, stops working on October 15. After that, it won’t run or get support.
To keep using Kualitee in Jira, install the new app before then. Your test data stays exactly as it is. Nothing is lost. You just switch over:
New to Kualitee and never used the old app? Skip all of this. Just install the new one, and you’re good.
A Few Quick Answers
I Use The Old App. Will I Lose My Data?
No. Your test data stays put. You’re moving to the new app, not rebuilding anything.
Do I Need a Kualitee Account?
Yes. The app links your Jira to Kualitee. No account yet? You can set one up when you install the app from the Marketplace.
What if I Don’t Switch in Time?
The old app stops working on October 15, so move before then to avoid any gap in your workflow.
The Short Version
Kualitee for Jira is now a full test management app, built natively on Atlassian Forge. It’s faster, safer, and steadier than the old one. On the old app? Switch before October 15. Your data comes with you. New here? This is the best Kualitee in Jira we’ve shipped.
Questions about the switch? Talk to our team, and we’ll help. Or grab the new app here.





