If youβre still manually tracking how long issues stay in Ready for QA β Done, this tool will save you time every single week.
Iβve built π οΈ Control Chart Snapshot Bot
β a ready-to-use open-source solution that:
- pulls data from Jira,
- calculates QA cycle time,
- generates a chart & summary stats,
- and automatically posts results into Slack.
You can plug it into your workflow today with just Jira + Slack tokens.
π§ How it works:
- Connect Jira API + Slack API
- GitHub Actions runs the script weekly
- Your Slack channel receives a snapshot with Mean / Median / P75 + histogram.
π Why itβs useful
- No more manual spreadsheets or Jira exports
- Weekly snapshot of QA performance
- Spot anomalies where issues stay in QA too long
- Improves visibility for both testers and managers
π Repository
π Code is open-source here
Iβd love your feedback, ideas, or Pull Requests.
My goal is to grow this into a practical open-source QA tool that any team can adopt.
π€οΈ Roadmap:
π Trend chart (7-day moving average)
π§© Component/Epic breakdowns
βοΈ YAML config & richer filters
π§ͺ Test execution correlation (Testomat integration)
π³ Dockerfile & Cloud Run job
π¬ Slack slash commands /qa-snapshot
β‘ If youβve ever struggled with collecting QA metrics or have ideas for useful visualizations, drop a comment below or open an Issue on GitHub.
Together we can make QA reporting more automated, transparent, and fun π
Top comments (0)