TroubleTicketSpecification
- Extends
TroubleTicketSpecification defines the common attributes and relationships of a set of related trouble tickets, while trouble ticket defines a specific instance that is based on a particular trouble ticket specification.
| 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 |
|
Unique identifier |
2d7ed5fd-9f62-4211-bc84-357f5f7b80f5 |
|
|
No |
No |
|
Hyperlink reference |
||
|
No |
No |
|
Name given to the specification |
EntityName |
|
|
No |
No |
|
Description of the specification |
Lorem ipsum dolor |
|
|
No |
No |
|
Date and time of the last update of the specification |
2023-01-01T08:00:00+01:00 |
|
|
No |
No |
|
Used to indicate the current lifecycle status of this catalog item |
active |
|
|
No |
No |
|
Determines whether specification represents a single specification (false), or a bundle of specifications (true). example: true |
||
|
No |
No |
||||
|
No |
No |
|
Specification version |
1.0 |
|
|
No |
No |
|
Attachments that may be of relevance to this specification, such as picture, document, media |
[] |
|
|
No |
No |
||||
|
No |
No |
|
List of characteristics that the entity can take |
[] |
|
|
No |
No |
|
Parties who manage or otherwise have an interest in this specification |
[] |