Creates a TroubleTicket
This operation creates a TroubleTicket entity.
Request
- Base URLhttps://serverRoot/tmf-api/troubleTicket/v4
- Authnone declared
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Request body
When sub-classing, this defines the sub-class entity name
When sub-classing, this defines the super-class
A URI to a JSON-Schema file that defines additional attributes and relationships
The date on which the trouble ticket was created
Description of the trouble or issue
The expected resolution date determined by the trouble ticket system
Additional identifier coming from an external system
The date and time that the trouble ticked was last updated
Name of the trouble ticket, typically a short description provided by the user that create the ticket
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...
The resolution date requested by the user
The date and time the trouble ticket was resolved
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
The date and time the status changed.
The reason for changing the status
represent a business type of the trouble ticket e.g. incident, complain, request
Possible values for the status of the trouble ticket
Response
Created
When sub-classing, this defines the sub-class entity name
When sub-classing, this defines the super-class
A URI to a JSON-Schema file that defines additional attributes and relationships
Unique identifier of the trouble ticket
Hyperlink, a reference to the trouble ticket entity
The date on which the trouble ticket was created
Description of the trouble or issue
The expected resolution date determined by the trouble ticket system
Additional identifier coming from an external system
The date and time that the trouble ticked was last updated
Name of the trouble ticket, typically a short description provided by the user that create the ticket
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...
The resolution date requested by the user
The date and time the trouble ticket was resolved
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
The date and time the status changed.
The reason for changing the status
represent a business type of the trouble ticket e.g. incident, complain, request
Possible values for the status of the trouble ticket
Changes
No recorded changes to this operation across all 1 revision of this API.