At a glance
Open Tickets is a backlog health metric tracked from Teamwork data. It surfaces operational signal at the backlog health layer so merchants can spot regressions, opportunities, and structural patterns in their store performance. The card pairs with sibling metrics in the Backlog Health category to build a complete diagnostic picture; cross-reference the related cards listed below for context.
| What it counts | Open Tickets as exposed by the Teamwork integration. The metric is computed from the latest available data and refreshed on the standard data refresh. |
| Sample type | Backend API data from Teamwork, refreshed on the standard data refresh. |
| Why it matters | The metric appears in the Backlog Health category and complements the sibling cards listed below. Track movement over time to identify regressions or opportunities. |
| Reading the value | Compare the current period to the prior period to identify direction. Cross-reference siblings for the full diagnostic picture. |
| Currency | number |
| Time window | RT |
| Alert trigger | >2Ã- 30D avg |
| Sentiment key | tea_open_tickets |
| Roles | owner, operations, developer |
Calculation
Calculated automatically from your Teamwork 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 representative reading of Open Tickets for a typical merchant on Teamwork. The card reports the current period value alongside a comparison against the previous period. Direction matters: rising values may be healthy or concerning depending on the underlying metric. Cross-reference the siblings below to triangulate cause when the value moves outside expected range. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
tea_backlog_by_priority | Backlog Health sibling: Backlog by Priority. |
tea_backlog_by_status | Backlog Health sibling: Backlog by Status. |
tea_blocked_tickets | Backlog Health sibling: Blocked Tickets. |
tea_in_progress_tickets | Backlog Health sibling: In Progress. |
tea_assignee_load | Team Capacity sibling: Tickets by Assignee. |
Reconciling against the vendor’s own dashboard
Where to look in Teamwork’s own dashboard: The Teamwork dashboard surfaces this metric (or its components) under the relevant report section. Confirm period boundaries and filter settings match the Vortex IQ profile to reconcile cleanly. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ uses 30-day rolling by default; vendor dashboards may use calendar periods. | Variable | Match the period range. |
| Time zone. Vendor uses account time zone; Vortex IQ aligns to merchant reporting time zone. | Marginal | Confirm time zone match. |
| Filter scope. Profile-level filters (channel, B2B, test orders) may narrow the Vortex IQ view. | Variable | Match filter settings. |