One issue tracker for problems that need attention
Bring software problems from different projects into one work list. AIOps collects findings from the tools already checking those projects, keeps the supporting details, and tracks whether the problems have actually been resolved.
The empty list was misleading
A review of more than 50 PickBits projects found no open issues in the tracker. But work was waiting in scattered project notes, along with 2,530 security detections that had not yet been reviewed. The information had not made it onto the work list.
What the tracker does
- Collects problems automatically. Findings arrive from the tools and project records that already contain them.
- Keeps one issue for one problem. Seeing the same finding again updates its record instead of creating another copy.
- Keeps the supporting details. A reviewer can see which project is affected and where the finding came from.
- Checks before closing. Two complete checks must show that the problem is gone. A failed or unfinished check cannot close it.
How a problem moves through the list
A connected tool finds a problem and sends it to the tracker. The person responsible reviews the details and any proposed action. Approval and carrying out the action are separate steps. The issue stays open until follow-up checks support closing it.
What changed
PickBits now uses one issue store fed by its existing sources. Getting a finding onto the list no longer depends on someone copying it from a separate file, and a quiet check is not treated as proof of a fix.
This is a tool built for PickBits' own operations. Its code is private and there is no public app to download. A similar setup for another business would need to connect to that business's projects and checking tools.
Have something like this in mind?
Tell Mark what you need people to be able to do. We can work out what to build, what it would cost, and what it will take to look after it.