One workspace for a QA team
A web app that pulls a QA team's Jira tickets and TestRail runs into one place, so engineers stop switching between tools. Mostafa's own product.
- Role
- Product owner and builder.
- Period
- 2026 – present
- Status
- MVP
- Stack
- Next.js 15, Supabase, Jira REST API, TestRail API, scheduled sync
- 15 minsync interval
- ~1,860test cases synced
- ~640tickets synced
Architecture
System steps in order
- Sources
- Jira API (Input). Feeds: Scheduler every 15 min
- TestRail API (Input). Feeds: Scheduler every 15 min
- Sync
- Scheduler every 15 min (Logic)
- Ingest and classify (Logic)
- Tickets, cases, runs, results, comments (Data). Feeds: Daily brief
- App
- Daily brief (Output)
- Coverage matrix (Output)
- Smart rerun (Output)
- Comment to Jira (Output)
- Next (planned)
- Role-scoped AI assistant (AI)
- Test case generation into TestRail (AI)
- Duplicate-bug detection (AI)
The problem
QA engineers lose time moving between Jira, TestRail and chat to answer simple questions: what changed, what failed, what needs a rerun.
What I built
A sync that refreshes Jira and TestRail data every 15 minutes into Supabase, and an app on top: a daily brief, ticket hierarchy with defect origins, a story-to-suite coverage matrix, smart rerun selection, classified comment feed, and posting Jira comments with mentions.
Key decisions
- Integrate, do not replace. Jira and TestRail stay the systems of record.
- Honest freshness. The UI shows when each source last synced.
- Cost per seat is a design constraint for the AI layer, so models are chosen per task.
Results
MVP in pilot use with an EdTech QA team. Numbers above are from the pilot data set.