Tickets we created from audit findings that haven’t been resolved yet.
At a glance
The number of Monday.com items in your Vortex IQ Findings board whose Status column value is not in the closed set. Monday is the visual board+timeline+gantt PM tool with strong colour-coded status fields, popular with marketing and agency teams. Status is a coloured label, not a free-text field; this card reads the structured Status column directly.
| What it counts | Items in the connected Monday.com board where the Status column label is not in the closed set (default closed labels: Done, Won't Do, Cancelled). Each item counts once. Subitems count separately if they have their own Status value. |
| API endpoint | Monday.com GraphQL (https://api.monday.com/v2), query { boards(ids: [<board_id>]) { items_page(limit: 500) { items { id, name, column_values(ids: ["status", "vortexiq_finding_id"]) { id, value, text }, updated_at } } } }, paged via cursor. The connector polls every 60 seconds plus listens to Monday’s webhook events for status changes. |
| Status filter | Items where column_values[id="status"].text is in the closed set are excluded. The closed set is configured at connector setup (default: Done, Won't Do, Cancelled); marketing teams sometimes add custom labels like Approved or Live, which need mapping. |
| Board scope | One Monday.com board per connected workspace, named at setup (Settings → Connectors → Monday → Findings board). Vortex IQ does NOT crawl other boards; your campaign timeline boards, CRM boards, and dashboard boards are invisible to this count. |
| Subitems | Counted independently if they have their own Status value. Most findings live as parent items; subitem findings are uncommon. |
| Workspace scope | All connected Monday.com workspaces (each Monday account can have many workspaces). Multi-workspace agencies typically connect each client workspace separately. |
| Time window | RT. Refreshed within 60 seconds via webhook plus the 60-second poll safety net. |
| Alert trigger | > 20 open raises a warn-level alert. |
| Time zone | Monday.com stores created_at and updated_at as ISO-8601 in your account-profile timezone; the GraphQL response normalises to UTC, which is what we use. |
| Multi-workspace aggregation | Yes; per-workspace stack panel available. |
| Roles | owner, operations |
Calculation
Calculated automatically from your Monday.com 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-based marketing-led DTC bedding brand on Shopify, 19-person team. Marketing operations runs Monday.com as the primary planning tool because the team prefers visual timeline views over kanban. Snapshot taken on 02 May 26 at 13:00 BST.| Monday.com Status (label) | Items | Counts as open? |
|---|---|---|
| Working on it | 9 | yes |
| Stuck | 3 | yes |
| In Review | 6 | yes |
| Approved | 2 | depends on mapping |
| Done | 14 | no |
| Cancelled | 2 | no |
| Won’t Do | 1 | no |
- Comfortable, just below warn. 18 open findings on a 19-person team with a marketing-led workflow is normal-busy; Monday teams typically run at the upper end of the open-count band because the visual board makes accumulation feel less stressful than on Linear or Basecamp.
- The Stuck cluster (3 items) is the read-now signal. Monday.com’s Stuck label is platform-idiomatic for “blocked”; three items in Stuck for an extended period is the cluster to triage first regardless of severity.
- The In Review cluster (6 items) is the most common Monday anti-pattern. In Review tends to become a parking space because the visual board makes it look active. Pair this card with Abandoned Findings to see how many of the 6 have been there 14+ days.
- The Approved mapping is the team’s call. Some teams treat Approved as resolved (signed off, work complete); others treat it as open (signed off but not yet shipped). The connector setup respects the team’s convention, this is a deliberate flexibility because Monday’s status taxonomy varies wildly between teams.
- Pair with Tickets by Assignee. Monday.com supports the People column with multiple assignees per item; this card shows the queue total, the assignee card surfaces concentration. On marketing teams the queue often clusters on the marketing operations lead.
Sibling cards merchants should reference together
On Monday.com, open count is the queue depth. Pair it with these to make decisions:| Card | Why it matters next to Findings Open | What the combination tells you |
|---|---|---|
| Abandoned Findings (>14d no movement) | Detects when Monday’s In Review and Stuck labels become parking spaces. | Open growing AND abandoned growing equals capacity problem; open growing + abandoned flat = active churn. |
| Finding Resolution Rate (90d) | The team’s batting average. | Resolution above 75% with open climbing equals over-finding; below 50% is an execution problem. |
| VortexIQ Findings In Progress | Counts items in Working on it-style labels. | Low in-flight share = items in queue but not picked up. |
| Avg Time-to-Fix (days) | Cycle time signal. | Open up + time-to-fix up = stretched team. |
| Tickets by Assignee | Where the queue concentrates by Person. | Marketing teams on Monday often see queue concentration on one ops lead. |
| Backlog by Priority | What’s open by importance (reads Monday’s Priority column). | If 80% of open is Low, close them rather than chase capacity. |
| Sprint Progress | Whether findings are entering a planned weekly batch. | Marketing teams using Monday timelines often run weekly batches; this card tells you if findings are getting into them. |
Reconciling against the vendor’s own dashboard
Where to look in Monday.com’s own UI:
monday.com then open the Vortex IQ Findings board. The default Main Table view shows all items; click the Filter button at the top toolbar and add Status → is not → Done, Cancelled, Won't Do (and any custom closed labels you have mapped). The bottom-of-board count reflects the filtered total. Save the view as Open Findings so the team always lands on it.
For a multi-board rollup, Monday’s Dashboards module supports a Numbers widget that counts items across multiple boards filtered by Status; pin one to a workspace dashboard to compare with this card.
Why our number may legitimately differ from the Monday filtered view:
| Reason | Direction | Why |
|---|---|---|
| Status label mapping | Either | We treat the configured closed-label set as resolved. If your team adds a custom label like Approved or Live to mean “shipped”, we count it open by default until you map it as closed in connector settings. |
| Subitem handling | Ours can be lower | We count subitems with their own vortexiq_finding_id; if the Monday view groups subitems under parents, the visible count may differ. |
| Time zone | Boundary day off | Monday’s UI uses your account-profile timezone; we align rolling windows to UTC. |
| Cross-workspace aggregation | Ours wider | Monday’s UI scopes to one workspace at a time; we sum across all connected workspaces. |
| Webhook delay vs polling | Ours up to 60s stale | We listen to status webhooks and poll every 60 seconds as a safety net. |
| Card | Expected relationship | What causes the divergence |
|---|---|---|
datadog.dd_incidents_active | Independent. Datadog tracks live engineering incidents; Monday tracks the planned remediation work for findings. | A Datadog incident closed without a Monday follow-up item means the underlying cause may not be addressed. Marketing-led teams using Monday rarely have direct Datadog correlations because the audit findings tend to be content/SEO rather than infrastructure. |
newrelic.nr_open_incidents | Same shape. | Same. |
Known limitations / merchant FAQs
My Monday board view shows 16 but Vortex IQ says 18. Why? The 2-item gap is the standard set of reasons in the reconcile section: status-label mapping (we count any label not in the closed set as open; your saved view may exclude additional labels like On Hold), subitem handling, and cross-workspace aggregation. Pin a per-workspace stack panel to compare. We added a custom Status label called Live and the count looks wrong. Why? Because Vortex IQ does not know whether Live means “shipped, work complete” (closed) or “live in market, monitoring” (open). At connector setup we seed the default closed set asDone, Cancelled, Won't Do; any new custom label needs explicit mapping. Open Settings → Connectors → Monday → Status mapping to add Live to the closed set if that is your team’s convention.
Subitems: do they count?
Yes, independently if they have their own vortexiq_finding_id value. Monday’s subitems are first-class items with their own Status, Person, and custom column values. Vortex IQ writes findings as parent items; subitem findings appear only if a teammate manually creates them.
Monday has multiple People columns. How do we read this card with that?
The open count is per-item, not per-person, so a multi-Person item counts once. The Tickets by Assignee card splits the load across all People on an item.
Open count dropped suddenly. What changed?
Three usual causes. (1) A bulk Status change (Monday’s Activity log on the board will show this). (2) A board was archived; archived boards return no items via the API. (3) A Status label was renamed or deleted (e.g. someone renamed Stuck to Blocked); items in that label may temporarily drop from the count until the new label is mapped.
A finding shipped but the Monday item is still in Working on it. Do we need to update it?
Yes. The Status column value is the close signal Vortex IQ reads. Click the cell and change to Done (or your team’s equivalent closed label). Monday’s keyboard navigation (Tab and arrows) makes this fast for batch updates.
Today’s count looks volatile. Why?
At low volumes a single Status change moves the count noticeably. The 30-day average shown beneath the headline is the steadier read. Monday teams typically see more volatility on this card than Linear teams because Monday’s visual board encourages more granular workflow stages, which means more individual transitions per day.
Is Monday.com the right PM tool for our context?
Monday shines for marketing/agency teams that benefit from visual board+timeline+gantt views and per-item people-tagging. It also has CRM features baked in that make it natural for marketing-led teams managing influencer campaigns and partner ops. The cost is configuration overhead at scale: large workspaces with 50+ boards become hard to govern, and the lack of a built-in cycle/sprint primitive means audit-finding work tends to drift. Asana’s strength is custom-fields-and-portfolios for cross-functional ops; Linear is closer for engineering teams; Smartsheet is closer for spreadsheet-style PMOs; ClickUp is closer for “everything-app” use cases; Teamwork is closer for time-tracking-driven agencies; Basecamp is closer for small calm-process teams.
My team uses Monday for marketing and Jira for engineering. Will Vortex IQ duplicate findings into both?
No. Each finding routes to one PM tool based on the connector setup’s outbound priority. Marketing-tagged findings route to Monday; engineering-tagged findings route to Jira. Override in Settings → Connectors → Routing.