You’re chasing metrics. But are your child tickets quietly blowing up your SLA reports behind the scenes?
As more TSPs double down on reporting accuracy and operational maturity, unexpected data issues are beginning to surface—one of the most common being open child or merged tickets that were never properly closed.
This isn’t just a cleanup task. Left unresolved, it can completely wreck your SLA, resolution time, and service performance reporting—even if your team did everything right on the parent ticket.
Let’s break down why it happens, why it matters, and what you can do to catch it before it skews your metrics beyond repair.
Note: It’s important to understand the difference between Child and Merged tickets. A child ticket can be detached and returned to a regular, standalone ticket. A merged ticket, however, is permanent and cannot be reversed once completed.
How Child & Merged Tickets Break SLA Calculations
In ConnectWise PSA, when a ticket is merged into another or childed under a parent, the system does not always prompt you to update the child’s status to a closed-type. Depending on how or where the merge/childing happens, these linked tickets can quietly remain in an open or active status.
That means:
-
The parent ticket can be closed…
-
But the child remains open…
-
And SLA tracking, resolution time, and action time continue to calculate based on that child ticket’s status.
We’ve seen real-world examples where this caused reporting to show SLA violations stretching over 3 years—even though the issue was resolved within a day. Why? The child ticket sat forgotten in “In Progress.”
If you’re using BrightGauge, Power BI, or even ConnectWise’s built-in reports, this will throw off:
-
SLA compliance rates
-
Time to resolution metrics
-
Time to first response
-
Aging ticket dashboards
-
Escalation tracking
Why This Gets Missed (And It Often Does)
Even in well-managed service environments, this problem sneaks through:
-
No system alert warns you about the open child after merging
-
Dispatchers and techs are often focused on the parent ticket
-
Managers reviewing time sheets don’t always catch the status of linked tickets
-
Workflows can’t chase children
And let’s face it—between onboarding, project work, escalations, and everything else on your team’s radar, manually checking the status of every child ticket just isn’t happening.
What You Should Be Doing
✅ 1. Use a Closed-Type Status for Child Tickets
Create a dedicated status like “Closed (Child) or Closed (Merged)” to clearly separate these from standard closures. This allows for clean reporting while preserving the link to the parent.
✅ 2. Update SOPs for Merging or Child Tickets
Train your team to update the child ticket’s status immediately after merging or linking. If your PSA doesn’t prompt for it, it should still become part of your documented process.
✅ 3. Audit Regularly
Even with good SOPs, things slip through. A monthly audit of open tickets that are linked as children can help you catch problems before they affect reporting.
Or Better Yet — Automate the Cleanup
Because this issue shows up so frequently in partner environments, Visionary 360 built an automated solution: the PSA Child Ticket Status Update module.
It scans your ConnectWise PSA environment, identifies child or merged tickets that are still sitting in an open status, and automatically updates them to a designated closed-type status—like “Closed (Child)”—based on logic you define.
This module is part of our Mass Maintenance Booster (MMB) suite—designed to solve real-world PSA pain points like this one.
Learn more: www.massmaintenancebooster.com
Wrap-Up
Clean, accurate reporting starts with clean data. If your SLA metrics seem off, don’t just look at the parent ticket. Check the children.
If left unattended, they will distort your dashboards, KPIs, and internal trust in the numbers.
Whether you do it manually or automate it with a tool like MMB, make sure child tickets are getting closed properly.
Your service board—and your reporting—will thank you.
