Issues

Capture defects and problems on your assets — surface inspection fails and driver reports before they become work orders

Issues

Issues capture problems and defects found on your assets — a fluid leak spotted during a walk-around, a brake squeal a driver flagged on the road, an inspection item that came back as a fail. Issues sit upstream of work orders: triage them, prioritise, and only promote to a work order once you're committing actual time and money to fix the problem.

Access issues from the sidebar under Fleet Management → Operations → Issues.

Why Track Issues Separately From Work Orders?

A work order represents committed maintenance — scheduled time, allocated parts, expected cost. An issue is just a report. Some issues turn into work orders, some get resolved at the next pre-trip inspection, some are noted and dismissed.

Keeping them separate means triage stays lightweight, your work-order pipeline isn't polluted with one-line "weird noise from the rear" reports, and nothing falls between the cracks of a failed inspection and the actual repair.

List View

The issues list shows every issue your role is permitted to see, with summary metrics across the top.

Statistics Cards

• Total Issues — every issue on the books
• Open — awaiting triage
• In Progress — being worked on
• Critical Open — priority = critical AND status not yet resolved or wont_fix (red when above zero)

Columns

Filters

• Status — Open, In Progress, Resolved, Won't Fix
• Priority — Low through Critical
• Source — Manual, Inspection, Driver App, System
• Saved Views — pin your common triage filters (e.g., "Critical & open this week")

Reporting an Issue

Click Report issue in the top-right of the list page. The drawer captures:

• Title (required) — one-line problem statement
• Description — longer explanation, what was observed, when, by whom
• Asset (required) — searchable picker
• Priority — defaults to Medium
• Photo — optional reference picture (helps the mechanic before they walk to the asset)

Hit Create and you're taken straight to the new issue.

Issue Sources

Every issue carries a source so you can tell at a glance how it landed in your queue.

The Inspection source is the load-bearing one — every time a checklist item comes back as a fail, an issue is created automatically with the inspection's photo, comment, and severity carried over. That means a fail can never be silently lost between inspection close-out and the workshop.

Triage Workflow

Issues follow a simple lifecycle:

Open  →  In Progress  →  Resolved
   ↓             ↓
   └────────→ Won't Fix

• Open → In Progress — set when somebody picks the issue up
• In Progress → Resolved — set when the underlying problem is fixed
• Open / In Progress → Won't Fix — set when the issue is intentionally dismissed (e.g., cosmetic damage you're choosing to ignore)

A linked work order doesn't auto-close the issue — you mark it resolved explicitly so the resolver and the mechanic don't have to be the same person.

Promote to Work Order

When an issue actually needs scheduled work — parts to order, labor to allocate, real time to commit — promote it to a work order from the issue detail page.

Click Promote to Work Order and the dialog pre-fills:

• Asset — copied from the issue
• Type — defaults to Corrective; pick another if you prefer
• Description — issue title + description merged
• Priority — copied from the issue

After confirmation:

• A new work order is created with all the issue context
• The issue's work_order_id field is set, linking the two records
• The issue stays Open / In Progress until you mark it Resolved (so the issue trail outlives the work order's lifecycle)

Inspection Auto-Promotion

For critical inspection failures, you can configure an automation that auto-promotes the resulting issue straight into a work order. Useful for fleets where a critical fail (e.g., brake defect on a DVIR) can't sit in triage — it has to be scheduled immediately or the vehicle goes out of service.

See Automations for the trigger setup.

Permissions

Best Practices

• Triage daily. A short morning sweep of Open issues keeps the queue manageable.
• Use Critical sparingly. Reserve it for safety-of-life or vehicle-out-of-service issues so the metric stays meaningful.
• Promote, don't duplicate. When an issue needs work, promote it — don't create a new work order from scratch and orphan the issue.
• Resolve the issue, not just the WO. The issue is the user-visible record; the work order is the maintenance ledger. Both need closing for a clean audit trail.
• Photos beat words. A picture of the actual defect saves the next person ten minutes of guessing.

FAQ

What's the difference between an issue and a work order? An issue is a report of a problem. A work order is a commitment to fix one. Multiple issues can promote to a single work order; some issues never get promoted at all.

Can I bulk-resolve issues? Yes — select multiple rows in the list view and use the bulk actions toolbar.

Why did my inspection fail not create an issue? Inspection auto-promotion fires on the inspection item's severity. If the item severity is set to informational, no issue is raised. Check the template's item severity if you expected an auto-created issue.

Can drivers see issues they didn't report? Drivers see issues against vehicles they're assigned to. Reporter visibility doesn't matter — assignment to the asset does.

Related Features

• Inspections — auto-promote inspection failures into issues
• Work Orders — promote an issue when it needs scheduled work
• Automations — auto-promote critical issues straight to work orders

Need Help?

Contact your organization administrator or the Yipii support team for assistance with issues configuration, automations, or permissions.