BEbell
troubleTicket

List or find TroubleTicket objects

This operation list or find TroubleTicket entities

get/troubleTicket

Request

Query parameters

fieldsstring

Comma-separated properties to be provided in response

offsetinteger

Requested index for start of resources to be provided in response

limitinteger

Requested number of resources to be provided in response

sortstring

To have the output sorted by fields. Can support one or many fields, as well as ascending and descending sort order

expandstring

Lists the sub-entities to expand along with the depth value. Empty means expand all at depth level N

depthstring

Depth level where objects are dereferenced and inserted as values into the response

Response

Success

@typestring

When sub-classing, this defines the sub-class entity name

@baseTypestring

When sub-classing, this defines the super-class

@schemaLocationstring uri

A URI to a JSON-Schema file that defines additional attributes and relationships

idstring

Unique identifier of the trouble ticket

hrefstring

Hyperlink, a reference to the trouble ticket entity

creationDatestring date-time

The date on which the trouble ticket was created

descriptionstring

Description of the trouble or issue

expectedResolutionDatestring date-time

The expected resolution date determined by the trouble ticket system

externalIdstring

Additional identifier coming from an external system

lastUpdatestring date-time

The date and time that the trouble ticked was last updated

namestring

Name of the trouble ticket, typically a short description provided by the user that create the ticket

prioritystring

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...

requestedResolutionDatestring date-time

The resolution date requested by the user

resolutionDatestring date-time

The date and time the trouble ticket was resolved

severitystring

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

statusChangeDatestring date-time

The date and time the status changed.

statusChangeReasonstring

The reason for changing the status

ticketTypestring

represent a business type of the trouble ticket e.g. incident, complain, request

status'submitted' | 'acknowledged' | 'rejected' | 'pending' | 'held' | 'inProgress' | 'cancelled' | 'closed' | 'resolved'

Possible values for the status of the trouble ticket

Changes

No recorded changes to this operation across all 1 revision of this API.