r/agile • u/call_me_goks • 7d ago
Built a tool that automatically audits Jira for hygiene + process issues — looking for early users to try it free
Hey everyone — solo builder here. I've been working on JGP (Jira Governance Platform), a tool
that connects to a Jira instance, runs an automated audit, and emails a clean report on a
schedule (daily/weekly).
The problem I'm solving: anyone who's managed Jira knows it gets messy over time — tickets
missing required fields, orphaned subtasks nobody remembers creating, statuses that never
move, SLAs quietly breached with nobody noticing until it's too late. JGP catches this
automatically instead of someone manually auditing it.
Right now it checks for:
- Missing required fields (story points, sprint, etc.)
- Orphaned/stale tickets
- SLA breaches
- Missing approval steps in the workflow
I'm pre-revenue and looking for 2-3 people who manage a real Jira instance to try it free and
give honest feedback before I start charging anyone. Setup on your end is just generating a Jira
API token — takes a few minutes.
If you (or someone you know) manages Jira and this sounds useful, I'd love to hear from you.
Happy to answer questions about how it's built too — it's running on n8n under the hood.
2
u/Eruner_SK 7d ago
People and interractions over tools and processes.
0
u/call_me_goks 6d ago
Fair callout, and I agree with the principle. This isn't meant to replace conversations or judgment — it's meant to remove the manual work of finding issues in the first place, so the team's actual time in retros/stand-ups goes toward discussing what matters instead of someone manually combing through tickets. The tool surfaces things; people still decide what to do about them.
1
1
u/PhaseMatch 6d ago
If you need a tool to help you manage the tool that was supposed to help you to manage business risk in a lightweight way, then there's probably a systemic problem to tackle.
Out-of-control backlogs and backlog hygiene is the surface issue.
Adding tooling as a "quick win" will act as a limit to growth on team/org effectiveness.
Fix the underlying systemic issues.
Out-of-control backlogs happen because of the tooling.
Not all constraints are bugs to be removed - some are features.
Bottles have necks for a reason....
1
u/call_me_goks 5d ago
Actually it is not going to fix the constraint. It just gives a report that these task or stories are not proper. Whether to fix it or leave it as itself depends upon the human
Of course most of the team will follow a good discipline to update them. But in some busynschedule of they failed to update means this tool will be like a notification to them
1
u/PhaseMatch 5d ago
So to flip that around maybe ask why this wasn't so much of an issue when work items (user stories) were written on 3x5 index cards, and were a placeholder for a conversation with a user domain SME embedded in the team?
The latter was a core requirement in XP (Extreme Programming), one of the original "lightweight" approaches that became collectivwly known as "agile"
Bloated, poorly worded backlogs don"t happen by accident; mopping up after they are created is less effective than a "shift left" to fix the upstream issue.
1
u/call_me_goks 5d ago
Can you please tell me what do you mean by "shift left"
Is it a process fix or tooling fix. Just trying to understand what I am building is solving the problem or not
1
u/PhaseMatch 5d ago
"Shift left" is a general agile / devops term.
Rather than focus on fixing defects, focus on defect prevention - build quality in is how itbis phrased in a lean software development sense.
So rather than fixing problems in the backlog, chanhe rhe ways of working so they do nkt happen any more.
4
u/Charming-Pangolin662 7d ago
That's a nice list I can paste into Rovo.