Ticket system; Tracks support requests with custodian, status and transaction history. Separating the incident, standard service request, and change record facilitates proper prioritization.
How to separate incident from service request?
Interruption of a running service event; A new account or access request may be treated as a service request. Atlassian explains this distinction with different workflows. For example, a disconnection request and a request to open an account for a new employee do not require the same priority criteria.
What should be included in a support ticket?
The service affected, the start of the problem, user impact, responsible and actions taken should appear. Priority should not be left only to the label chosen by the person who opened the request; should be evaluated along with business impact and urgency. Sample records are not presented as actual customer results.
Check when setting up support flow
- Separate incident, service request, and change categories.
- Define assignment, hold, resolution, and reopen states.
- Measure initial response and resolution time separately; Include working hours in the measurement.
Reference source: Atlassian — Separation of service request and incident management. Implementation details should be evaluated according to the current environment and current regulations.
Related resources
For application and enterprise support coverage IT Service and Enterprise IT Support You can review the page.
Official sources
Technical documentation and legislation may change; The relevant version and current text should be checked before application.
Frequently Asked Questions
Does opening a ticket mean that the problem is solved?
No. Creating a record, assigning responsibility, and verifying the solution are separate steps.
Is the initial response and resolution time the same?
No. The initial response is a separate measurement that indicates that the request has been addressed, while the resolution indicates that the issue has been resolved.