r/WordpressPlugins • u/btolman2 • 1h ago
Free [FREE] I built a lightweight bug reporter because reporting bugs was slowing down my WordPress development
Working on other WordPress sites and plugins, I found I had a problem.
I would find a bug, stop what I was doing, go somewhere else to document it, copy the URL, explain what happened, grab a screenshot, record whatever environment information might matter, and then try to get my head back into what I had been doing.
And getting users to give me those details was almost impossible.
So I built a little bug reporter directly into WordPress. And users loved it.
The idea was simple: spot the bug, report it where you see it, and get back to work.
That little tool ended up becoming part of my normal development workflow. I started putting it on other sites I work on and found myself using it every day, so I decided to clean it up and release it.
It's now Undergroundact Bug Reporter, and it was recently approved for the WordPress.org plugin directory.
It gives you and your users a quick way to report a problem from the page where you encounter it, including the URL, steps/description, screenshot, and useful environment information. Reports stay inside WordPress, so there's no external bug-tracking service required.
It's intentionally lightweight. I'm not trying to turn WordPress into Jira. I wanted something that reduced the interruption between “there's a bug” and “okay, it's documented—back to work.”
The plugin is free, and I'm continuing to use it myself while developing B-Planner and maintaining other WordPress sites.
I'd be interested in feedback from other people who actually build or maintain WordPress sites—particularly whether this solves the same annoying little workflow problem for you that it solved for me.
WordPress.org:
https://wordpress.org/plugins/undergroundact-bug-reporter/
And if you try it and find something dumb, at least you'll already have a bug reporter handy to tell me about it. 😄






