Toine.com B.V. on the Atlassian Marketplace
Reporting apps
for test teams
I build useful tools and apps. The ones on this page are small reporting apps for test and delivery teams. Each app does one thing: show what was tested, what was found and what is ready to go live. They only read your data and they run on Atlassian Forge, so your data stays on Atlassian.
Release Readiness for Jira
Marketplace listing in preparation
One page that shows whether a release is ready to go live.
You set the criteria per release yourself, whatever your definition of done is: open blockers, failed tests, work without tests, defects above a certain severity. The app checks them against live Jira data and shows you which ones are met, which are at risk and which are not met. It also lists the work that has no test evidence at all. Admins sign off on the same page, and every sign-off and every change is kept.
Criteria
You get a set of starter criteria, each one a JQL threshold you can change. There are project defaults, personal views and an admin lock for when the definition should not change anymore.
Evidence
Test status comes from the issues linked to the work. Stories and bugs without a linked test show up as not checked. That number is usually missing from the report.
Sign-off
Project admins, the project lead and groups you name can sign a release off as ready or not ready, with a note. The roles come from Jira. I don't keep a separate list inside the app.
History
A daily snapshot per release and a decision log that nothing gets deleted from. Six weeks after go-live you can still see what was green that day and who signed off.
Where you find it: a project page, a dashboard gadget, a project settings page and a global overview. Jira Cloud only. The interface is in English.
Price: paid through Atlassian, per user, monthly or yearly, with the usual 30 day free trial once it's listed. I'll publish the price with the listing.
What's next
I want to do the same for the other reports that test and delivery teams keep rebuilding in Excel. I'm thinking of defect health and ageing, exploratory testing sessions, a one page test summary report and a register of AI systems for the EU AI Act. On the documentation side: test plans and test reports, decision logs, RAID logs and lessons learned.
It stays one app per problem, read-only and on Forge. New apps show up on this page first.
How I build the apps
Read-only
The apps ask for read access to Jira work items and users, plus their own app storage. They never write to your issues, don't change workflows and don't create anything in your project.
Data stays on Atlassian
Everything runs on Atlassian Forge. Configuration, snapshots and sign-offs are stored in app storage on your own site. I don't run a server for it and no data goes out. No third party analytics either.
One job per app
No suite with modules you never open. Every app answers one question.
Built by a test manager
I've been running SIT, UAT and chain tests for 20+ years, for pension funds, government and media. The reports in these apps are the ones I made by hand every week.
Support
Questions, bugs and feature requests go by email. I answer within two working days, usually a lot faster. Please add your Jira site URL, the name of the app and a screenshot if you have one. Security issues go first, put "security" in the subject line.
- Support email
- contact@toine.com
- Response time
- Two working days, Monday to Friday, CET
- Privacy
- Privacy policy for the apps
- Terms
- Terms and licence
Vendor
- Marketplace vendor
- Toine.com B.V.
- Chamber of Commerce
- 87544903
- VAT
- NL864325381B01
- Based in
- Utrecht, the Netherlands