TrueStory
QA testing for Jira with AI test generation and PR gating
Start new thread
Njegos Ignjic

TrueStory - QA testing for Jira with AI test generation and PR gating

by•
Most QA tools were built by people from the paperwork era. Ok, teams use them. TestRail, Zephyr, spreadsheets. But they work the way filing cabinets work. TrueStory is inside Jira, natively, in tickets,projects,settings. Writing test cases (step by step or Gherkin) is a pleasure with AI agent you pick, using ticket info and defined prompt. New PRs create test session and can remain blocked until test passes. QA before the merge, not a bugfix after the damage. Proactive against reactive approach.

Add a comment

Replies

Best
Njegos Ignjic
Maker
📌
Hey everyone! Straight to the point. We built this for two reasons. First, QA tools we see felt like they belonged in a different universe. Jira on one screen, TestRail on another, a spreadsheet somewhere for the stuff that didn't fit either. But the main point we saw is misalignment with project management and code being pushed to repositories. Last I saw, the ultimate effort is to mention Jira ticket in a branch name, and it will be connected to that branch, ticket moved to swimlane when code gets updated. So we built TrueStory directly inside Jira. Test cases live on the tickets. AI writes them from ticket context, you pick the provider (Anthropic, OpenAI, DeepSeek, Gemini) and define the prompt. For selected AI agent, it is client who provides API key, we don't want to collect anything. When a PR opens on GitHub, Bitbucket, or GitLab, a testing session is created automatically and the merge stays blocked until QA passes. This has other options of course, to avoid bottlenecks. The idea is simple: test before the merge, not after the fire. We're a small crew with big opinions about how QA should work. We'd love to hear yours. Happy to answer anything.