> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # VortexIQ Findings Open, Asana > Tickets we created from audit findings that haven't been resolved yet. How to read it, why it matters, and how to act on it. **Metrics type:** [Key Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Project Management](/nerve-centre/connectors#connectors-by-type) > Tickets we created from audit findings that haven't been resolved yet. ## At a glance > The number of Asana tasks Vortex IQ created from audit findings that have not yet reached a `Completed` state. Each row is a real piece of work (an SEO regression, a broken canonical, a stale meta description, a feed-failure incident) that an audit raised and pushed into your team's project plan. If this number grows faster than your team closes it, the audit programme is finding faster than you can fix. | | | | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Open Asana tasks where `custom_fields.vortexiq_finding_id` is set AND `completed = false`. One task = one finding. | | **API endpoint** | `GET /tasks?project={project_gid}&completed_since=now&opt_fields=custom_fields,assignee,due_on,modified_at`, paged via `next_page.offset`. Asana REST v1.0 base `https://app.asana.com/api/1.0`. | | **Task status filter** | `completed = false` only. Tasks marked completed via Asana's checkmark or the API are excluded the moment Asana's webhook fires. | | **Closed tasks excluded** | Yes. A task in a "Closed" or "Won't Do" section is still excluded only if it has been ticked complete; orphan tasks moved to a closed section but never marked complete still count (Asana lets sections and completion drift apart). | | **Archived projects** | Excluded. Tasks in archived Asana projects are ignored even if `completed = false`. The `archived: true` project flag is the gate. | | **Project / workspace scope** | All Asana projects in the connected workspace where Vortex IQ has push permission, intersected with the projects tagged in the connector setup as `vortex_iq_outbound`. Multi-workspace merchants connect each workspace separately; this card aggregates across all connected workspaces unless filtered. | | **Time window** | `RT`. Real-time, refreshed within 60 seconds of the Asana webhook firing. | | **Alert trigger** | `> 20 open` raises a warn-level alert. The 20 threshold reflects the typical merchant ratio of 1 finding per 5 GMV-relevant SKUs; tunable per organization. | | **Sentiment** | None directly; pair with `asa_vortexiq_findings_abandoned` and `asa_vortexiq_finding_resolution_rate` for the trend reading. | | **Time zone** | Asana stores `due_on` as a date (no timezone) and `modified_at` as ISO-8601 UTC. Vortex IQ aligns the `RT` window to UTC for cross-connector arithmetic. | | **Multi-workspace aggregation** | Yes when more than one Asana connection exists. Each workspace's open count is summed; the dashboard shows the blended total with a per-workspace stack panel available. | | **Roles** | owner, operations | ## Calculation Calculated automatically from your Asana 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 direct-to-consumer skincare brand on Shopify, 18 person team, runs Asana for marketing and product operations. Snapshot taken on 02 May 26 at 09:15 BST. | Project (Asana) | Open VortexIQ findings | Notes | | ------------------------- | ---------------------- | ---------------------------------------------------------------------------------------- | | Marketing Operations | 14 | Mostly meta description and Open Graph image regressions on the new collection pages. | | Site Reliability | 6 | Two recurring feed-failure incidents from BigCommerce sync, four broken-canonical fixes. | | Catalogue & Merchandising | 9 | Missing structured data on bundles; assigned to the catalogue lead. | | Customer Experience | 4 | Returns-policy URL drift between footer, knowledge base, and checkout. | | **Total open** | **33** | Above the 20-task warn threshold. | ```text theme={null} Open count 33 Warn threshold 20 (>20 fires) Critical threshold none (warn only) 30D average 22 Delta vs 30D avg +50% ``` **What the merchant should read into this:** 1. **The number is above warn.** 33 open findings means the audit programme is identifying issues faster than the team can close them. Either staff up the response, ruthlessly defer non-revenue findings, or accept the backlog will grow. 2. **Most of the queue sits in Marketing Operations.** This is normal because marketing has the highest cadence of content and tag changes. The risk is that low-severity meta-description findings accumulate while a single high-severity catalogue regression sits behind them. 3. **Four CX findings on returns-policy drift** is the highest-leverage cluster on the list. Returns-policy mismatches between footer and checkout are a known conversion killer (shoppers abandon when the policy they read at the bottom of the page contradicts what they see at checkout). Triage these first, regardless of count. 4. **Pair this card with [Abandoned Findings](/nerve-centre/kpi-cards/asana/abandoned-findings).** A growing open count is acceptable if the team is closing fast enough; an abandoned-rate spike alongside a growing open count is the real warning sign. 5. **Compare against [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/asana/finding-resolution-rate).** If resolution rate is above 75% but the open count still climbs, the audit programme is over-finding for the team's capacity, not under-fixing. ## Sibling cards merchants should reference together Open count is rarely useful on its own. 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)](/nerve-centre/kpi-cards/asana/abandoned-findings) | The leading indicator that the open queue is stagnating. | Open growing AND abandoned growing equals capacity problem; open growing but abandoned flat equals normal active backlog. | | [Finding Resolution Rate (90d)](/nerve-centre/kpi-cards/asana/finding-resolution-rate) | Tells you whether the team is keeping up with intake. | Resolution > 75% with open climbing equals over-finding by the audit; resolution \< 50% equals execution problem. | | [VortexIQ Findings In Progress](/nerve-centre/kpi-cards/asana/vortexiq-findings-in-progress) | Splits the open queue into "actively being worked" vs "queued". | High in-flight share equals the team is engaged; low in-flight share equals findings are being noted but not picked up. | | [Avg Time-to-Fix (days)](/nerve-centre/kpi-cards/asana/avg-time-to-fix) | The headline cycle-time number for findings specifically. | A rising open count plus a rising time-to-fix is the combined signal of a stretched team. | | [Tickets by Assignee](/nerve-centre/kpi-cards/asana/tickets-by-assignee) | Shows where the open queue concentrates. | If 80% of open findings sit on one person, that's a single-point-of-failure risk to fix this week. | | [Overloaded Assignees (>10 open)](/nerve-centre/kpi-cards/asana/overloaded-assignees) | Counts the people whose individual queues are blocking throughput. | One overloaded assignee plus high open count plus high abandoned rate equals reassign this person's queue today. | | [Sprint Progress](/nerve-centre/kpi-cards/asana/sprint-progress) | Tells you whether findings are getting into sprints at all. | Findings that never enter a sprint are the ones that go abandoned. | ## Reconciling against the vendor's own dashboard **Where to look in Asana's own UI:** > **[app.asana.com](https://app.asana.com/0/home)** then open each project tagged as `vortex_iq_outbound` in your connector setup. Switch the project to **List** view, click the **Filter** button at the top, and add two filters: `Custom Fields → vortexiq_finding_id → is set`, then `Completion → Incomplete`. Click **Save view as** if you want a permanent dashboard. Asana also exposes a workspace-level [search builder](https://app.asana.com/0/search) which can query across all projects in one go using the same filters. For multi-project portfolios, use **Portfolios** (Asana Premium / Business / Enterprise) and pin the same filtered view there. **Why our number may legitimately differ from Asana's filtered view:** | Reason | Direction | Why | | ------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Time zone** | Boundary day off | Asana's `due_on` is a date with no timezone; Asana's UI uses your account-profile timezone for "today/this week" filters. Vortex IQ aligns the `RT` window to UTC. For a real-time count this rarely changes anything, but for date-bounded comparisons (e.g. "tasks created today") the window may include or exclude one boundary day. | | **Archived project handling** | Ours lower | Asana's workspace-wide search includes archived projects by default; we exclude them. To match, untick "Include archived projects" in Asana's filter. | | **Section vs completion drift** | Ours higher | A task moved to a "Closed" or "Done" section without the checkmark is still incomplete in Asana's data model. We count it. Asana's UI reports it correctly but a kanban-trained eye assumes "in the closed column = closed". | | **Custom-field deletion** | Ours lower | If a finding's `vortexiq_finding_id` custom field was manually cleared, the task disappears from this count even though it is still open in Asana. Audit the connector's custom-field write history if you suspect this. | | **Cross-workspace aggregation** | Either | Asana's UI scopes to one workspace at a time; this card sums across all connected workspaces. Filter by workspace in the connector drawer to match a single-workspace view. | | **Webhook delay** | Ours up to 60s stale | If a teammate just clicked complete in Asana's UI, our count may take up to 60 seconds to drop. Asana's UI updates instantly; ours updates on the next webhook delivery. | **Cross-connector reconciliation. Asana vs incident-management peers:** | Card | Expected relationship | What causes the divergence | | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`datadog.dd_incidents_active`](/nerve-centre/kpi-cards/datadog/active-incidents) | Independent. Datadog tracks live engineering incidents (server-side); Asana tracks the planned remediation work for findings (audit-side). They should not be the same number. | A Datadog incident closed without an Asana follow-up task means the underlying cause may not be addressed. A Vortex IQ finding raised without a Datadog signal means it is content/SEO/catalogue, not infrastructure. | | [`newrelic.nr_open_incidents`](/nerve-centre/newrelic/nr_open_incidents) | Same shape as Datadog comparison. | Same divergence reasons. |
Documentation cross-reference (for agencies running multiple PM tools) The same metric exists with the same definition across other PM tools we connect to. This is **not** a reconciliation, your team uses one PM tool. These references exist purely so an agency running clients on multiple PM tools can cross-link the same metric across docs. * [`trello_api.tre_vortexiq_findings_open`](/nerve-centre/kpi-cards/trello-api/vortexiq-findings-open) * [`clickup.cli_vortexiq_findings_open`](/nerve-centre/kpi-cards/clickup/vortexiq-findings-open) * [`monday.mon_vortexiq_findings_open`](/nerve-centre/kpi-cards/monday/vortexiq-findings-open) * [`linear.lin_vortexiq_findings_open`](/nerve-centre/kpi-cards/linear/vortexiq-findings-open) * [`basecamp.bas_vortexiq_findings_open`](/nerve-centre/kpi-cards/basecamp/vortexiq-findings-open)
## Known limitations / merchant FAQs **My Asana view says I have 28 open findings but Vortex IQ says 33. Which is right?** Both, almost always. The five-task gap is the standard set of reasons listed in the reconcile section: archived projects (we exclude, Asana's workspace search may include), section/completion drift (a task in a "Done" section that was never ticked complete still counts to us), webhook delay (a tick-complete from the last 60 seconds may not be reflected yet), and cross-workspace aggregation (we sum across all connected workspaces, Asana's UI scopes to one). Open the per-workspace stack panel to reconcile. **Why does the count include tasks already in our "Done" section?** Because Asana's data model treats sections and completion as independent. Moving a card to a "Done" column does NOT mark it complete; only the checkmark or `completed = true` via the API does. If your team's workflow is to drag-and-drop into Done without ticking complete, the count will look high. Fix: enable Asana's **Rules** (Premium) to auto-complete tasks when moved to your Done section. **We use multiple Asana workspaces (one per agency client). What does this card show?** It sums findings across every Asana connection in your organization by default. If you have three workspaces connected, the headline number is the total. Open the connector drawer's **Stacked panel** view to see them broken out. **A finding was important enough to fix manually but we never used the auto-created Asana task. Do we need to close it?** Yes. Tick complete (or set `completed = true` via API) on the auto-created task once the work is done in your codebase. Otherwise the finding stays in this card's count and contributes to the abandoned-rate timer (14 days of no movement). Vortex IQ does not auto-close findings just because the underlying audit signal cleared on the next run; the human acknowledgement is the close signal. **Open count dropped suddenly. What changed?** Three usual causes, in order of likelihood. (1) An assignee did a bulk close (the Asana audit log under **Admin Console → Audit Log** will show this). (2) A project was archived (archived projects' tasks drop out of the count immediately). (3) Vortex IQ paused outbound finding creation due to an account-level pause; check the connector status in **Settings → Connectors**. **Why doesn't this number match the count of recent VortexIQ findings on my dashboard?** The Vortex IQ findings count and the Asana open count diverge by design. The findings count is what the audit found across the last 7 / 30 / 90 days; this card is what Asana currently has open. Older findings that were resolved drop out of this card but stay in the long-window finding totals. **Is Asana the right PM tool for our context?** Asana shines for cross-functional ecommerce teams that mix marketing, ops, and CX work in one place. If your team is engineering-heavy with sprints, milestones, and a heavy GitHub-issue cadence, Linear is a closer fit. If your team is dev-shop-style and uses kanban boards almost exclusively, Trello is lighter-weight. If your team is marketing-and-agency-led with strong visual planning, Monday is its peer competitor. Asana's strength here is **portfolios**: an ops director with five concurrent projects (catalogue, marketing, CX, returns, integrations) gets a single rollup that no other PM tool matches. The other strength is **custom fields** at the workspace level, which is what makes the `vortexiq_finding_id` round-trip clean. **My team uses Asana but you also have Jira connected. Will Vortex IQ duplicate findings into both?** No. Each finding is routed to one PM tool based on the connector setup's outbound priority. Default is Jira if connected (engineering-led), Asana if not. Override in **Settings → Connectors → Routing** if your operations team owns the queue regardless of engineering involvement. **Today's count looks volatile. Why?** At very low volumes (\< 5 open findings) a single close or a single new finding moves the count by 20%+ which can register as visual noise. The 30-day average (shown beneath the headline number) is the steadier read for trend purposes; the headline number is the live count. *** ### Tracked live in Vortex IQ Nerve Centre *VortexIQ Findings Open* is one of hundreds of KPI pulses Vortex IQ tracks across Asana 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.