Skip to content
ERPNext Data Model
Esc
navigateopen⌘Jpreview
On this page

Support

Issue tracking with Service Level Agreements, issue types, priorities and warranty claims.

Post-sales service: Issue, Service Level Agreement, Warranty Claim.

What it does

Support turns inbound customer problems into tracked Issues. Each Issue carries a type, a priority and a customer, and a Service Level Agreement computes its response-by and resolution-by targets from working hours and holidays — then flags the Issue when either is missed. Warranty Claim covers serial-numbered items still under warranty or AMC.

Key features

  • Issue — status, type, priority, customer/contact, and first-response and resolution timestamps.
  • Service Level Agreement — per-priority response and resolution targets, support and holiday schedules, and pause conditions.
  • Priority and type masters — Issue Priority and Issue Type drive both routing and SLA selection.
  • Warranty Claim — serial-number-based claims against warranty or AMC expiry dates.
  • Email integration — issues raised and threaded directly from an inbound support mailbox.

Entity relationships

Each diagram below is one connected cluster of entities. Edges are labelled with the fieldname that carries them — see relationship notation for how to read the crow’s feet.

Issue

Issue is the support case hub, linking the customer query to its type, priority, service-level agreement, and warranty context.

Document composition

Parent documents and the child tables they own.

Parent Table field Child table Req
Service Level Agreement pause_sla_on Pause SLA On Status
Service Level Agreement priorities Service Level Priority yes
Service Level Agreement sla_fulfilled_on SLA Fulfilled On Status yes
Service Level Agreement support_and_resolution Service Day yes

Entity reference

Look it up

Was this page helpful?