Tickets we created from audit findings that haven’t been resolved yet.
At a glance
The live count of sticky notes / shapes on the configured Mural where the VortexIQ-finding tag is present and the item has not been moved to the team’s “done” area. Mural is a workshop-led whiteboard (acquired by LumApps in 2024), so this card primarily serves teams that run audit triage as facilitated sessions rather than continuous flow. Expect different rhythm than Miro: spikes on workshop days, flat between them.
| What it counts | Items on the configured Mural tagged vortexiq:finding where the item is NOT inside a frame named “Done” (case-insensitive). Mural’s “done” semantics rely on facilitator-set frames (containers), not column position, so the connector reads frame membership rather than coordinates. |
| Mural / room scope | The single Mural configured on the connector. Mural’s “rooms” group multiple murals; the connector targets one mural at a time. Cross-mural roll-ups need separate connections. |
| Status filter | ”Open” means anything not inside a Done frame. Items outside any frame still count as open (the floating-on-the-canvas pattern). |
| Item type filter | Sticky notes, shapes, and Mural’s native “icon” items where the vortexiq:finding tag is present. Connectors (lines), text labels, and embedded media are skipped. |
| Resolution counts | A finding leaves the count when someone drags it into a frame named “Done” or deletes the item. Mural facilitator features (timer, voting, summary export) do NOT close items automatically. |
| Time window | RT (Mural API polled every 60 seconds; webhook-driven when supported). |
| Alert trigger | >20 open, same calibration as Miro / Asana. Mural workshops can briefly spike above this and the alert engine widens its tolerance during known-workshop windows when the team flags them. |
| Roles | owner, operations |
Calculation
Calculated automatically from your Mural 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 wellness brand on Adobe Commerce runs quarterly audit-triage workshops on a Mural called Q2 Storefront Audit Triage 26. The mural has four facilitator frames: Inbox, Owned, In delivery, Done. Vortex IQ creates one sticky per audit finding, taggedvortexiq:finding.
Snapshot taken on 02 May 26 (today) at 14:00 EDT, two days after a workshop session:
| Frame | Stickies tagged vortexiq:finding |
|---|---|
| Inbox | 7 |
| Owned | 12 |
| In delivery | 6 |
| Done | 28 |
| Floating (not in any frame) | 2 |
- 12 in Owned are assigned but not yet picked up. Within the next 5 working days these usually move to In delivery.
- 7 in Inbox are unowned. Friday’s standup will assign them.
- 2 floating items are leftovers from the workshop sticky-storm; one is a duplicate of an Owned item.
vortexiq:reference.
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. The “stuck after the workshop” tail. | Mural-specific gotcha: workshop-week items have a 5-7 day grace period before abandonment looks meaningful; abandonment after 14 days post-workshop is the real signal. |
| Finding Resolution Rate (90d) | The flow ratio. Workshop cadence makes this swing more than Miro’s. | A healthy 70%+ rate is the post-workshop catch-up signal. Sub-50% means the workshops are intake-only, no delivery follow-up. |
| Throughput Trend | Closure rhythm by week. Mural teams cluster closures near workshop weeks. | Bimodal trend (spike then flat) is normal for workshop-led teams; flat trend without spikes means the team is not running review sessions. |
| VortexIQ Findings Resolved (90d) | The completion peer. | Confirms whether workshop output is converting to delivery. |
| Miro VortexIQ Findings Open | Visual-collab peer. Miro is real-time-flow oriented; Mural is workshop-oriented. | Same metric, different rhythms. Comparing the two helps an agency understand which surface their client prefers. |
| Jira VortexIQ Findings Open | The engineering-canonical peer. | Mural for facilitator-led discovery; Jira for engineer-led delivery. Both populated means dual-track operations. |
Reconciling against the vendor’s own dashboard
Where to look in Mural’s own dashboard: Mural does not provide a native “open work-items” dashboard. The closest manual reconciliation is to open the configured mural and use the Tags panel to filter byvortexiq:finding, then visually count stickies outside the Done frame.
Mural app → open the configured mural → click the magnifying-glass icon → search vortexiq:finding → toggle “Show only matching items” → manually count stickies that are NOT inside the Done frame.
Because Mural uses frame-membership rather than column-position for status, the team’s “Done” frame must be named exactly Done (case-insensitive) for the connector to recognise it. If the team renamed it to “Shipped” or “Closed”, set done_frame_name in the connector config.
Why our number may legitimately differ from a manual count:
| Reason | Direction | Why |
|---|---|---|
| Frame-name match | Either | If the Done frame is renamed and the connector config is not updated, all items appear “open” indefinitely. |
| Floating items | Ours higher | Items dropped outside any frame count as open here; merchants visually scanning may discount them as “draft”. |
| Polling cadence | Ours stale up to 60s | API polled minutely. Webhook support is partial; some Mural plan tiers do not expose realtime events. |
| Voting / facilitator features | None | Mural’s voting and timer features change visual state but not item state; they do not affect this count. |
| Permission scope | Possible undercount | The Mural API only returns items the connector’s OAuth user can see. If a frame is private to a sub-team, those items are invisible to Vortex IQ. |
| Time zone | None | Real-time count, no period boundary. |
| Card | Expected relationship | What causes the divergence |
|---|---|---|
miro.mir_vortexiq_findings_open | Same metric, different visual-collab tool. | Teams generally pick one tool; both populated implies migration in progress. |
lucidchart.luc_vortexiq_findings_open | Same metric, but Lucidchart is documentation-first; routing audit findings to Lucidchart is uncommon. | Expect divergent populations; treat as a courtesy peer. |
jira.jir_vortexiq_findings_open | The engineering-canonical peer. Mural is the discovery surface; Jira is the delivery system. | Mural higher than Jira often means the team triages on Mural and only escalates a subset to Jira. |
Known limitations / merchant FAQs
My team uses Mural for workshops, not for ongoing tracking. Should this card even fire alerts? For workshop-only teams, the answer is “yes but tune the threshold”. Workshop weeks legitimately push the count above 20 for 1-2 weeks while the team digests output. Two approaches: (1) raiseopen_alert_threshold to 35 if your team runs monthly workshops with heavy intake; (2) flag known workshop windows in the connector config (workshop_grace_days: 14) so the alert engine widens its tolerance for two weeks after each workshop.
Mural was acquired by LumApps in 2024. Does anything change for this connector?
The Mural product API has remained stable through the LumApps integration so far. We monitor changes via the Mural changelog and update the connector if endpoints move. As of May 26 there are no breaking changes; the connector targets the v0 (LumApps-era) API stable surface.
Why does the connector use frame-membership for status, not tag-state?
Mural does not have a native “status” enum. Frames are the most reliable status signal because facilitators set them up explicitly during workshops, and the labels (Inbox, In progress, Done) follow industry-standard Kanban conventions. Tags exist but they are user-defined and not consistently applied for status purposes; the connector uses tags only for category (severity:high) and identity (vortexiq:finding).
Items I deleted yesterday still show in the count. Why?
Mural’s API has a 5-15 minute eventual-consistency window on deletions. Webhook support is partial across plan tiers; on plans without webhooks the connector relies on polling and may be a full minute behind. If you see ghosts persist longer than 15 minutes, check the connector’s last-sync timestamp in Vortex IQ → Settings → Connectors → Mural.
Can I filter by severity?
Not on this card directly. The card returns the unfiltered open count. To see severity breakdown, open Backlog by Priority, which groups by severity:* tag. The summary card on the dashboard preserves a single number for at-a-glance reading; the breakdown lives in the dedicated chart.
My Mural is private to a sub-team. Does the connector see it?
Only if the OAuth user that connected Mural has read access to that mural. Vortex IQ never elevates permissions; the count is whatever the connector identity can see. To audit access, log in to Mural with the same account and verify visibility manually.
The connector’s auto-tag is vortexiq:finding. My team uses bug already. Will both apply?
Yes, tags are additive in Mural. The auto-dispatcher applies vortexiq:finding regardless of any other tags the team sets. The card filter is strict on vortexiq:finding, so a team-applied bug tag without the auto tag will NOT count. To promote a manually-added sticky into VortexIQ tracking, add the vortexiq:finding tag yourself.
Why is this card useful for a non-engineering merchant?
Because Mural is where workshop-led teams (UX, design, brand) decide what gets fixed. If the open count is high, the team has identified problems but is not closing them, which over weeks becomes “the dashboard is the same broken thing every time I look at it”. The card translates qualitative workshop output into a quantitative state the founder can monitor without reading the canvas.
The mural got renamed last week and the count went to zero. What happened?
Mural URLs change when the title is edited; the connector targets the mural by ID, not by URL, so renames are usually transparent. Going to zero suggests a different mural was selected (e.g. someone duplicated the mural and the connector still points at the old one). Re-select the mural in Vortex IQ → Settings → Connectors → Mural.