Tickets we created from audit findings that haven’t been resolved yet.
At a glance
Live count of pages or database rows Vortex IQ created in your Notion workspace from audit findings, that you haven’t moved into a “Done” status yet. This is your unworked-finding queue.
Calculation
Calculated automatically from your Notion data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A UK fashion brand on Shopify uses a Notion database called Site Improvements as their lightweight ticketing system (the team prefers Notion over Jira). Vortex IQ writes findings into this database. Snapshot taken on 12 Mar 26. The Site Improvements database has 47 rows taggedvortexiq:finding, with the following status distribution:
>20). The merchant’s owner-dashboard banner reads “33 unworked Vortex IQ findings, queue grew by 8 this week”. The follow-up cards (Avg Time-to-Fix, Finding Resolution Rate) tell them whether the queue is growing because findings are arriving faster, or because the team is closing them slower.
Why the “Won’t fix” rows don’t count: during connector setup the merchant mapped the Notion Won’t fix status into the Done group, signalling “we’ve decided, stop counting it”. This is the recommended pattern, abandoning a finding closes it for KPI purposes; it does not delete the page.
Sibling cards merchants should reference together
Open Findings is a queue depth, not a verdict. Read it next to these:Reconciling against the vendor’s own dashboard
Where to look in Notion itself: Notion does not have a vendor “dashboard” the way Jira or Datadog do. The closest equivalent is a filtered view of your Findings database:Open the Findings database → click the view dropdown at the top → New view → Board (or Table) Filter:The row count at the bottom of that filtered view should match this card exactly (within the sync window, see below). Why our number may legitimately differ from your Notion view:Statusis notDone(or whichever group you mapped to closed). Group: byStatus. Optional: filterTagscontainsvortexiq:findingto exclude any rows the team added manually.
Cross-connector reconciliation. Notion vs Jira / Linear / ClickUp:
If you also have Jira, Linear, or another ticketing system connected, the Findings counts there are not the same population. Vortex IQ writes findings to one mapped destination per workspace. Pick the system your team actually triages in, the others won’t carry findings.
Known limitations / merchant FAQs
Why is my Open count rising? Three usual reasons, in order of likelihood:- Inflow exceeds outflow. New findings keep arriving (audits, scheduled scans) but the team isn’t moving rows to Done at the same rate. Check Finding Resolution Rate (90d); if it’s below 60%, the team is genuinely behind. Add capacity, downgrade priority of low-value findings, or batch-close ones you’re not going to action.
- Status mapping drift. Someone added a new status value to the Notion database (e.g. “On hold”) that isn’t mapped to either To-do, In progress, or Done. Notion’s API still returns it, and we count it as open by default. Map it in Settings → Connectors → Notion → Status mapping.
- Findings going to the wrong database. If your team uses several Notion databases and a recent integration setup pointed Vortex IQ at the wrong one, you’ll see a confusing rise. Reconfigure the destination database in connector settings.
vortexiq:finding tag to any sub-page only if it’s genuinely a separate finding.
What if a teammate manually creates a row tagged vortexiq:finding?
It will count. The tag, not the creator, is the signal. This is intentional, it lets you migrate older findings into the system or hand-create a finding from a customer email and have it tracked alongside the auto-generated ones.
Why is “20 open” the alert threshold? Our team handles more than that comfortably.
The default is calibrated for a small ecommerce team (1, 5 people working on findings). Larger teams should raise it in Settings → Connectors → Notion → Alerts → Open findings threshold. The right number is roughly 2× your weekly resolution rate, e.g. if you typically close 15 findings per week, set the alert at 30, that’s two weeks of unworked queue.
Can the card distinguish between “untouched” and “in progress”?
Open is the rolled-up number. For the breakdown, look at Backlog by Status. The hero card stays a single number on purpose, you scan it in 1 second and decide whether to drill down.
My status names are in another language (French / German). Does it still work?
Yes. Notion’s status property uses internal status-group IDs (todo / in_progress / done), not the visible label. So “À faire” / “En cours” / “Terminé” works exactly the same as the English. The only thing that has to be in English is the vortexiq:finding tag (we write it, so it always is).