Just spent two days trying to get a coherent workflow out of AuditBoard's Action Plan module. Our security team insists on using it for tracking remediation, but the interface and logic seem to fight you at every turn.
The main pain points:
* **Status vs. Progress:** The difference between "In Progress" status and the manual "% Complete" field is never defined. Which one actually drives reporting?
* **Dependency mapping:** You can link issues, but there's no visual DAG or clear path. If Issue B depends on A, and A is rejected, does B auto-fail? No visibility.
* **Notification spaghetti:** We get alerts for "updates" that are just someone adding a comment. No way to filter alerts to only status changes or due date modifications without custom rules that require admin help.
I set up a test with three linked action items. Here's the absurdity: the "Roll-up Status" report in the dashboard showed "On Track," but the export to CSV for the same data showed one item as "Delayed." Which system of record is it?
Has anyone deciphered a consistent mental model for this module, or built external dashboards (Grafana, even a script) to pull the data and make sense of it? I'm looking at their API docs, but if the core data relationships are muddy, piping it out won't help.
What's your operational experience? Are we configuring it wrong, or is this a known quirk?
shift left or go home
Oh, the status vs. progress confusion is so real. In our setup, the "% Complete" field is purely manual commentary and doesn't gate anything. The "Status" field (like In Progress, Completed) is the only thing that triggers workflow changes and drives the high-level reporting. It's a weird separation.
For the reporting mismatch, we hit that too. The dashboard uses a cached summary view, but the CSV export pulls live data. The delay can be hours, which is why you see "On Track" vs. "Delayed". We ended up building a simple Power BI connector to pull data directly via the API for a single source of truth. It bypasses a lot of the UI ambiguity.
On notifications, our admin did set up a custom rule for us that only fires on status changes and new assignments. It took a support ticket, but it cut the noise by about 70%. Maybe push your security team to request that?