Hi Community — I’m Robert at JSoft. I work on Testing tool (Marketplace: Testing Tool for Jira). Full disclosure up front.
Testing tool is a Forge app designed for Runs on Atlassian — compute, storage, and Rovo inference stay on Atlassian, so it scales with your Jira Cloud site for any team size. Requirements, TestCases, and TestExecutions live on the project page (not a TMS only QA opens). Rovo’s Testing Agent can draft TestCases and writes only after you confirm.
Pricing:
• Free for sites with up to 10 users — same product surface as paid
• Paid plans when you grow past that — check Marketplace for current tiers
What you get:
• Project hub: Requirements, Test Design, Test Execution
• Issue panels on stories / TestCases / TestExecutions
• Test Pad for manual runs
• Rovo Testing Agent (confirm-before-write) — uses your site’s Rovo credits, not a separate AI meter from us
• Works with Atlassian Rovo MCP — manage TestCases from coding tools: Claude, Cursor, and GitHub Copilot
• CI ingest from common pipelines (GitHub Actions, GitLab, Azure, Bitbucket, Jenkins) when you are ready
We are in public beta and want real feedback from teams running test management inside Jira.
Marketplace:
https://marketplace.atlassian.com/apps/2615451138/testing-tool-for-jira
Setup / Ask flow docs:
https://ai-testing-tool.github.io/
If you run QA or quality work on Jira Cloud: try it, then tell me in the comments what blocked you in the first hour — missing work types, Rovo/MCP, coding tools, or CI setup. I will answer in-thread.
