Skip to main content
Card class: Hero • Category: Project Management
Tickets we created from audit findings that haven’t been resolved yet.

​
At a glance

The number of ClickUp tasks Vortex IQ created from audit findings that have not reached a status of type closed. ClickUp’s strength is its custom-status spectrum (each List can define its own statuses across open, custom, and closed types) which we read directly. The card answers across all my Lists, how much audit work is still in flight?
What it countsClickUp tasks where the custom field vortexiq_finding_id is set AND status.type ≠ 'closed' AND archived = false.
API endpointGET /api/v2/list/{list_id}/task?archived=false&include_closed=false&custom_fields=[…]&page=N from https://api.clickup.com/api/v2. We page until last_page = true.
Status-type filterWe exclude status.type = 'closed'. ClickUp lets each List define its own status names, but every status maps to one of four types: open, custom, done, closed. We treat closed as resolved; done is treated as not-yet-resolved (because some teams use “done” as a review-pending state before “closed”).
Archived tasks excludedYes (archived = false filter on the request).
Archived Lists / SpacesExcluded server-side (the API returns no tasks for archived containers).
SubtasksCounted independently if they have their own vortexiq_finding_id. Most findings live as parent tasks; we do not aggregate subtasks under their parent for this count.
Workspace scopeAll ClickUp Lists tagged vortex_iq_outbound in the connector setup, across all Spaces in all Workspaces connected.
Time windowRT. Refreshed within 60 seconds of ClickUp’s webhook firing.
Alert trigger> 20 open raises a warn-level alert.
Time zoneClickUp stores date_updated and date_closed as Unix epoch milliseconds (UTC). Vortex IQ aligns the RT window to UTC.
Multi-workspace aggregationYes. Each ClickUp Workspace’s open count is summed; per-workspace stack panel available.
Rolesowner, operations

​
Calculation

Calculated automatically from your ClickUp 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 US-based mid-market apparel brand on BigCommerce with a 32-person team using ClickUp as the all-in-one workspace (tasks, docs, sprints, and chat). Snapshot taken on 02 May 26 at 09:00 EDT.
Space → ListCustom statusesOpen count
Marketing → Campaign Ops”Open”, “In Review”, “In Progress”, “Done” (closed)18
Catalogue → Product Onboarding”To Do”, “Photography”, “Copywriting”, “QA”, “Live” (closed)12
Engineering → Site Reliability”Backlog”, “In Sprint”, “Code Review”, “Released” (closed)9
CX → Tickets”New”, “Working”, “Awaiting Customer”, “Resolved” (closed)5
Total open44
Open count           44
Warn threshold       20  (>20 fires)
30D average          27
Delta vs 30D avg     +63%
What the merchant should read into this:
  1. Above warn, by a meaningful margin. A 32-person team with 44 open audit findings is workable but stretched. ClickUp’s custom-status spectrum makes the queue visible in detail, open the List view in each Space and the spread across statuses tells you whether work is queued, in flight, or in review.
  2. Marketing (18) and Catalogue (12) drive most of the queue. This is the typical pattern for an apparel brand running seasonal collections: campaign launches and product onboardings spike audit findings together. Plan for it, don’t treat the next collection drop as a surprise event.
  3. Engineering’s 9 open is healthy. Engineering teams using ClickUp’s Sprint feature typically run leaner numbers because every task either enters a sprint or gets archived. If your engineering List is climbing, check whether sprints are actually closing.
  4. The “Awaiting Customer” status counts as open here. ClickUp considers it status type custom (not closed). Some teams prefer to exclude this status because it represents work the team can’t progress; if you want this excluded, mark the status as closed type in ClickUp’s status settings (this is reversible) or request a per-status exclusion in connector setup.
  5. Pair this card with Abandoned Findings. ClickUp’s custom-status flexibility makes “stuck in review” patterns very common; abandoned-rate tells you if those reviews are actually moving.

​
Sibling cards merchants should reference together

CardWhy it matters next to Findings OpenWhat the combination tells you
Abandoned Findings (>14d)Detects when ClickUp’s custom statuses become parking spaces.Open growing AND abandoned growing equals capacity; open growing + abandoned flat = active backlog.
Finding Resolution Rate (90d)Team’s batting average.Resolution > 75% with open climbing = over-finding by audit; < 50% = execution problem.
VortexIQ Findings In ProgressSplits open into “actively worked” vs “queued”.Low in-flight share = work in custom-status purgatory.
Avg Time-to-Fix (days)Cycle time signal for findings.Open up + time-to-fix up = stretched team.
Tickets by AssigneeClickUp supports multiple assignees per task; this card surfaces concentration.Heavy concentration on one assignee = reassignment opportunity.
Overloaded Assignees (>10 open)Single-point-of-failure detection.One overloaded + high open = queue-review priority.
Sprint ProgressClickUp Sprints (Sprint folders) commitment progress.Low sprint progress + high open = findings being noted but never sprinted.

​
Reconciling against the vendor’s own dashboard

Where to look in ClickUp’s own UI:
app.clickup.com then for each vortex_iq_outbound List, switch to List view, click Filter, add Custom Field → vortexiq_finding_id → has any value AND Status → is not Closed. The Dashboards module (ClickUp Unlimited and above) supports a “Tasks by status” widget filtered the same way for a multi-List rollup. ClickUp’s Workload view also surfaces open-task-by-assignee which is useful next to this card.
Why our number may legitimately differ from a ClickUp Dashboard widget:
ReasonDirectionWhy
Time zoneBoundary day offClickUp UI uses your account-profile timezone for “this week / today” filters; we align rolling windows to UTC. For a real-time count this rarely changes anything.
Status-type interpretationEitherWe treat status.type = 'closed' as resolved. If you have custom statuses with type done (which we keep open), the dashboard widget filtered “Status is not Closed” matches us; the widget filtered “Status is not Done OR Closed” will be lower.
Archived containersSameBoth we and ClickUp’s filter exclude archived Lists/Spaces. Match should be tight.
Subtask aggregationEitherOur count treats subtasks with vortexiq_finding_id as independent items. If your dashboard widget collapses subtasks under parents, the widget will be lower.
Custom-field deletionOurs lowerIf vortexiq_finding_id was cleared on a task, we drop it. ClickUp’s filter respecting “has any value” matches us, but a teammate viewing the List directly sees the task.
Cross-workspace aggregationOurs widerWe sum across ClickUp Workspaces; a Dashboard widget is per-Workspace.
Cross-connector reconciliation. ClickUp vs incident-management peers:
CardExpected relationshipWhat causes the divergence
datadog.dd_incidents_activeIndependent. Datadog tracks live engineering incidents; ClickUp tracks the planned remediation work.A Datadog incident closed without a ClickUp follow-up task means the underlying cause may not be addressed.
newrelic.nr_open_incidentsSame shape.Same reasoning.

​
Known limitations / merchant FAQs

My ClickUp List view shows 38 open tasks but Vortex IQ says 44. Which is right? Both, almost always. The 6-task gap is the standard set of reasons in the reconcile section: status-type interpretation (we treat status.type = 'closed' as resolved; if your List has custom statuses with type done that you visually treat as closed, we keep counting them open), subtask aggregation (we count subtasks with vortexiq_finding_id independently; the List view may collapse them under parents), cross-workspace aggregation (we sum across connected Workspaces; the UI scopes to one), and webhook delay (a status change in the last 60 seconds is not yet reflected). Refresh in 60 seconds and the gap usually closes. ClickUp lets each List define its own statuses. Which ones count as open? Every ClickUp status maps to one of four types: open, custom, done, closed. We count open, custom, and done as open (i.e. unresolved); we count only closed as resolved. This matches ClickUp’s own data model (the platform itself uses status.type as the primary completion signal). If you want a custom status excluded (for example, an “Awaiting Customer” status that represents work the team genuinely cannot progress), change its type to closed in Space Settings → Statuses or contact support to add a per-status override in connector setup. We use ClickUp Sprints. How do they interact with this card? ClickUp’s Sprint folders are special folder types where each list represents one sprint. Findings written into a Sprint folder follow normal status rules; a finding’s status type is what matters, not which sprint it sits in. The benefit is that Settings → Connectors → ClickUp → Sprint visibility lets you scope this count to “current sprint only” or “current + next sprint” if your team works on a strict sprint cadence. Subtasks: do they count? Yes, independently if they carry their own vortexiq_finding_id. ClickUp lets a parent task have many subtasks, each with its own status, assignee, and custom-field values. We treat each subtask as its own finding when it has the custom field set. This typically does not happen because Vortex IQ writes findings as parent tasks; it can happen if a teammate manually creates subtask findings. ClickUp has multiple assignees per task. How do we read this card with that? The open count is per-task, not per-assignee, so multiple-assignee tasks count once. The Tickets by Assignee card splits the load across all assignees on a task, so a task with three assignees contributes one to each. Some teams find this inflates per-person workload counts; if your team uses multi-assignee as “primary + reviewers”, request the connector setting to count only the primary (first) assignee. Open count dropped suddenly. What changed? Three usual causes, in order of likelihood. (1) A bulk close (ClickUp’s Audit log under Workspace Settings → Audit log will show this). (2) A List or Space was archived; archived containers return no tasks. (3) A status was renamed or moved to a different type group (e.g. Done moved from done to closed type in Space Settings); the open count drops because tasks in that status are now considered resolved. A finding was important enough to fix manually but we never closed the task. Do we need to close it? Yes. ClickUp’s status.type = 'closed' is the close signal Vortex IQ reads. If the work shipped but the task is still in an open or custom status, it stays in this count and contributes to abandoned-rate after 14 days. Move the task to a closed-type status to clear it. Open count doesn’t match my Dashboards “Tasks by status” widget. Why? A ClickUp Dashboard widget filtered to one Workspace will be lower than this card if you have multiple Workspaces connected. Filter the widget to “All workspaces” (Enterprise plan) or pin a per-Workspace stack panel here in Vortex IQ to compare apples-to-apples. 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. ClickUp teams typically see more volatility on this card than Asana or Basecamp teams because ClickUp’s custom-status spectrum encourages more granular workflow stages, which means more individual transitions per day. Is ClickUp the right PM tool for our context? ClickUp shines for mid-market teams that want one tool to do everything (tasks, docs, sprints, chat, time-tracking, goals, dashboards). The cost is configuration overhead: the more custom statuses you create, the more decisions Vortex IQ needs about which count as resolved. Asana’s strength is custom-fields-and-portfolios for cross-functional teams; Linear’s strength is keyboard-fast cycle-time for engineering teams; Monday’s strength is visual planning for marketing-and-agency teams; Smartsheet’s strength is spreadsheet-style PMO rollup. ClickUp’s strength here is the per-task time-tracking and goal-linking that we do not currently consume; if your team uses those features heavily, the connector setup may evolve to surface them in Vortex IQ.

​
Tracked live in Vortex IQ Nerve Centre

VortexIQ Findings Open is one of hundreds of KPI pulses Vortex IQ tracks across ClickUp and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.