TroubleTicketFVO
- Extends
| Field | Required | Nullable | Type | Description | Constraints | Example |
|---|---|---|---|---|---|---|
|
Yes |
No |
|
When sub-classing, this defines the sub-class Extensible name |
||
|
No |
No |
|
When sub-classing, this defines the super-class |
||
|
No |
No |
|
A URI to a JSON-Schema file that defines additional attributes and relationships |
||
|
No |
No |
|
Name of the trouble ticket, typically a short description provided by the user that create the ticket |
||
|
No |
No |
|
Description of the trouble or issue |
||
|
Yes |
No |
|
Date when the order was posted by the requester |
2023-01-01T08:00:00+01:00 |
|
|
No |
No |
|
The severity of the issue. Indicate the implication of the issue on the expected functionality e.g. of a system, application, service etc.. Severity values can be for example : Critical, Major, Minor |
||
|
Yes |
No |
|
Represent a business type of the trouble ticket e.g. incident, complain, request |
||
|
No |
No |
|
File(s) attached to the trouble ticket. e.g. pictur of broken device, scaning of a bill or charge |
||
|
No |
No |
||||
|
No |
No |
|
The resolution date requested by the user |
||
|
No |
No |
|
|||
|
No |
No |
|
The note(s) that are associated to the ticket. |
||
|
No |
No |
|
The priority of the trouble ticket and how quickly the issue should be resolved. Example: Critical, High, Medium, Low. The value is set by the ticket management system considering the severity, ticket type etc… |
||
|
No |
No |
|
An entity that is related to the ticket such as a bill, a product, etc. The entity against which the ticket is associated. |
||
|
No |
No |
|
The related party(ies) that are associated to the ticket. |
||
|
No |
No |
|
A list of trouble ticket relationships (TroubleTicketRelationship [*]). Represents a relationship between trouble tickets |
||
|
No |
No |
|
List of characteristics of the trouble ticket |