Tickets we created from audit findings that haven’t been resolved yet.
At a glance
The live count of Wrike tasks Vortex IQ created from audit findings that have not been moved to aCompletedorCancelledstatus. Wrike is the enterprise PM tool of choice for mid-market and enterprise marketing / ops teams (custom workflows, custom fields, resource management, time tracking, formal approval gates). Because Wrike workflows can be elaborate, “open” here means “not in any state mapped to the WrikeCompletedgroup”, regardless of how many custom intermediate states the team has defined. This card is calibrated to enterprise rhythms, expect slower flow but more disciplined closures than on lightweight trackers.
| What it counts | Wrike tasks in the configured Space whose customFields.Source equals vortexiq (or which carry the vortexiq:finding tag) and whose status.group is not Completed or Cancelled. Each finding maps 1:1 to one Wrike task; de-duplication is on the vortexiqFindingId custom field. |
| Space / project scope | The Wrike Space configured on the connector. Multi-Space rollups are supported by configuring multiple connector instances (one per Space). Tasks in sub-folders and sub-projects of the configured Space are included; tasks in Personal spaces are not. |
| Status group mapping | Wrike’s status model has 5 system groups: Active, Completed, Deferred, Cancelled, Custom. “Open” means anything not in Completed or Cancelled, so Active, Deferred, and any custom non-terminal status all count. Deferred tasks intentionally count as open because they are waiting for something, not finished. |
| Issue type filter | All Wrike task types. Wrike’s “task” is generic; the team’s custom workflow defines whether it represents a bug, story, request, or initiative. Subtasks of a parent VortexIQ-finding task are NOT counted separately, the parent is the unit of accounting. |
| Resolution counts | A finding leaves the count when its status moves into the Completed or Cancelled group. Re-opens (Completed → Active) re-add it to the count. Wrike’s approval workflow can also gate closures, a task in the Pending Approval custom status counts as open until approved. |
| Custom workflow handling | Most enterprise Wrike Spaces define custom workflows (e.g. In Review, Awaiting Stakeholder, Pending Legal, Ready for QA). Vortex IQ reads status.group not status.name, so workflows that map their custom states to the Completed group close cleanly; workflows that put closure-equivalent states in the Custom group need a one-time mapping in connector.wrike.completed_status_ids. |
| Time window | RT (Wrike REST API polled every 60 seconds; webhook-driven on Business plans and above). |
| Alert trigger | >20 open. Calibrated against typical enterprise audit cadence, mid-market merchants on Wrike receive 8-15 audit findings per cycle and >20 standing typically signals either a stalled approval gate or a real capacity problem. |
| Roles | owner, operations |
Calculation
Calculated automatically from your Wrike (API) 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 enterprise B2B brand on Adobe Commerce, ~120 person team. Marketing ops, performance, and ecommerce engineering all run delivery on Wrike, with a Storefront Operations Space configured as the connector target. Audit findings are dispatched into a sub-folder called VortexIQ Audit Backlog with a custom 5-state workflow. The custom workflow:| Status name | System group | Counts as open? |
|---|---|---|
| New | Active | Yes |
| Triaged | Active | Yes |
| In progress | Active | Yes |
| Pending stakeholder | Custom | Yes |
| Pending approval | Custom | Yes |
| Done | Completed | No |
| Won’t fix | Cancelled | No |
| Status | Tasks tagged vortexiq:finding |
|---|---|
| New | 5 |
| Triaged | 6 |
| In progress | 4 |
| Pending stakeholder | 7 |
| Pending approval | 3 |
| Done | 89 |
| Won’t fix | 12 |
- Of the 25 open, 10 are sitting in approval-gate states (Pending stakeholder + Pending approval). On Wrike enterprise workspaces this is the most common cause of a high open count, the work is done, the approvers are slow.
- 6 of the Triaged items have
customField.OwnerGroup = Marketing Opsand have not moved in 11+ days. - 4 of the In-progress items are tagged
severity:critical(checkout-script Adobe Commerce errors flagged by Datadog).
Sibling cards merchants should reference together
| Card | Why pair it with VortexIQ Findings Open | What the combination tells you |
|---|---|---|
| Abandoned Findings (>14d no movement) | Subset of Open that has gone cold. On Wrike the abandoned tail is often approval-gate dwell time, not actual neglect. | Abandoned rising in the Pending stakeholder state means an organisational unblock is needed (escalate the approver), not a team capacity intervention. |
| Finding Resolution Rate (90d) | The 90-day flow ratio. Counterweight to the live snapshot. | Open above 25 with rate below 50% means the workflow itself is the bottleneck, not intake. Audit and simplify approval gates. |
| Throughput Trend (30d) | Weekly closure rhythm. Multiplied by 4 should approximate monthly intake at steady state. | Open count divided by weekly throughput equals weeks-of-work standing. 25 open at 4/week is roughly 6 weeks of backlog; review whether the gate dwell-time is the cause. |
| VortexIQ Findings Resolved (90d) | The completion peer. Same population, opposite end of the funnel. | Open + Resolved over 90 days equals total intake. Use the ratio to grade audit-programme actionability on Wrike specifically. |
| Datadog Operational Health Score | If Datadog health is dropping while Open is rising, the team is detecting more issues AND fixing fewer of them. | Worst-case combination, escalate on-call rotation. |
| Jira Findings Open | Cross-tracker peer for teams that mix Wrike (marketing / ops) and Jira (engineering). | Engineering-owned findings on Jira, marketing / ops-owned on Wrike. Both populated is the typical enterprise pattern; the gap reveals the boundary between the two delivery surfaces. |
| Critical Findings Without a Jira Ticket | Coverage-gap card. Routing-rules sanity check. | If criticals are landing on Wrike instead of Jira, the auto-router is wrong, criticals belong on the system that escalates and pages, not the one that approval-gates. |
Reconciling against the vendor’s own dashboard
Where to look in Wrike’s own dashboard:Wrike workspace → open the Space configured on the connector → use the Filter button → setFor Business / Enterprise plans, Wrike’s Reports feature can render the same query as a saved chart, Reports → New Report → tasks → filter by Source field → group by status → exclude Completed and Cancelled groups. The total reconciles within polling lag. Why our number may legitimately differ from Wrike:Custom field "Source" equals vortexiqANDStatus group is Active OR Custom OR Deferred→ the result count in the filter footer matches this card.
| Reason | Direction | Why |
|---|---|---|
| Polling cadence | Ours stale up to 60s | REST API polled every 60 seconds on Free / Professional plans; webhook-driven on Business+. |
| Custom workflow mapping | Possible mismatch | If the team adds a custom status (e.g. Shipped) and intends it as a closure but does not map it to the Completed system group, Vortex IQ counts it as open. Manual reconciliation in Wrike via the same filter would give the same answer; the gap is between intent and configuration. Map the custom status via Space settings → Workflows → Edit. |
| Sub-folder boundary | Either | If the team moved tasks into a sub-folder outside the configured Space, the connector loses sight of them. The Wrike UI shows them; this card does not. Configure additional connector instances per Space if cross-Space rollups are needed. |
| Approval gate handling | Same in both | Tasks in Pending Approval states count as open in both Wrike’s filter and this card. No discrepancy expected unless approval is implemented via a separate Wrike Approval object (rare). |
| Recycle bin | Wrike higher in some views | Wrike’s “All tasks” view sometimes includes recently-deleted tasks for 30 days. This card excludes deleted tasks immediately. |
| Time zone | None | Real-time count, no period boundary. |
| Card | Expected relationship | What causes the divergence |
|---|---|---|
jira.jir_vortexiq_findings_open | Definitional twin if the team mixes Wrike (marketing / ops) and Jira (engineering). The same audit finding rarely dispatches to both, the auto-router decides based on severity and domain. | Jira count typically reflects engineering-owned findings; Wrike count reflects marketing / ops-owned findings. Both populated is the enterprise norm. |
asana.asa_vortexiq_findings_open | Lightweight-PM peer. Asana and Wrike sometimes co-exist in larger orgs (Asana for team tactics, Wrike for cross-team ops). | Different audiences, different cadences. Compare only if the same audit feed dispatches to both. |
monday.mon_vortexiq_findings_open | Direct competitor in the work-management tier. | Most enterprises pick one; both populated implies migration in flight. |
Known limitations / merchant FAQs
Why is my Wrike open count higher than my peer brand’s Jira count for the same intake? Wrike’s enterprise workflows include formal approval gates that Jira does not enforce by default. A finding that goes straight to Done on Jira often makes a stop in Pending stakeholder or Pending approval on Wrike, which inflates standing open counts by 30-50% on most enterprise workspaces. The 20-item threshold for Wrike calibrates against this; do not compare absolute open counts across the two tools without normalising for gate dwell-time. My team uses Wrike’s approval workflow on every audit task. The open count is always above 20. Should I worry? Probably not. If 50%+ of your open count is consistently in approval-gate states, the workflow is doing what it should, the throughput sibling card is a better signal than the open-count card for your specific setup. Pin the Resolution Rate card on the dashboard instead and let it be the headline; treat the open count as a secondary indicator. The auto-router put a critical Datadog finding into Wrike instead of Jira. Why? Two possibilities. (1) The routing rule for that severity / domain pair points at Wrike intentionally; check Vortex IQ → Settings → Audit routing. (2) Jira was unreachable when the dispatcher fired (auth token expired, organisation suspended), and the dispatcher fell back to the configured secondary tracker. Critical findings should always have Jira (or another paging-capable tracker) as primary, set Wrike as fallback only. Why does this card matter to a non-engineering merchant? Because Wrike is increasingly the system of record for marketing operations, brand-led teams, and cross-functional initiatives that touch ecommerce. If the open count is rising, your marketing-ops team is collecting more audit findings than they are acting on, which over weeks shows up as “the brand audit issues never get resolved”. This card is the early-warning version of that complaint, surfaced before the next QBR. A teammate manually added thevortexiq:finding tag to a Wrike task they created. Will it count?
Yes. The tag is the filter. Manual additions count, by design (anyone on the team can promote a task into VortexIQ tracking). The downside is that manual additions do not get a vortexiqFindingId custom field, so they cannot be deduplicated against the audit feed, if the dispatcher later creates a finding for the same issue, you may see two tasks for one underlying problem.
My Wrike Space has multiple sub-folders for different product areas. Are they all counted?
Yes. The configured Space scans recursively, so tasks in Storefront Operations / Apparel / VortexIQ Audit Backlog count the same as tasks in Storefront Operations / Footwear / VortexIQ Audit Backlog. If you want per-area counts, configure separate connector instances pointing at the leaf folders, which gives you per-area cards on the Nerve Centre.
Can I trust Wrike’s webhooks for real-time updates?
On Business and Enterprise plans, yes. Wrike’s webhook delivery is reliable and median-latency 300-700ms. On Free / Professional plans, polling is your only option and the count can lag up to 60 seconds. If the merchant is making decisions based on minute-by-minute readings, upgrade to Business.
Should this number ever be zero?
No, and zero usually indicates a problem. Audit detection runs continuously and enterprise teams have steady intake; zero either means auto-dispatch is broken (findings not reaching Wrike), the Source custom field is misconfigured, or the team has bypassed Wrike entirely. A healthy enterprise Wrike workspace shows 8-18 standing items at any moment.
The count dropped sharply after we re-organised the Space. Is something wrong?
Three usual causes. (1) Tasks were moved to a Space the connector cannot see, reconnect or move them back. (2) The bulk re-org changed the Source custom field on tasks (Wrike’s bulk-edit can be aggressive), restore the field via Wrike’s audit log. (3) The team moved tasks into the Recycle Bin during the cleanup, those are excluded from the count immediately even though Wrike’s UI may still show them for 30 days.
Wrike has a “Backlogged” status group concept. How is it treated here?
Wrike’s Deferred group is what most teams call “backlogged” (work that is intentionally on hold). This card counts Deferred tasks as open because they represent unfinished work the team has committed to. If you want to exclude truly long-deferred items (e.g. parked-indefinitely), move them to Cancelled with a won't fix reason; do not leave them in Deferred where they continue to inflate the count.