Relationship of additional states and fields to DevOps WorkItem properties
The relationship of the states between the platforms and the additional fields is represented by the following JSON:
{
"model": [
{
"reference": "",
"id": 0,
"state": [
{
"value": "",
"id": 0,
"reason": 0,
"commentary": {
"Key": "",
"value": ""
}
}
],
"additionalFields": [
{
"id": 0,
"field": {
"key": ""
},
"value": [
""
],
"mapping": [
{
"id": 0,
"value": ""
}
]
}
]
}
]
}
Where:
Properties
| Properties | Description | |
|---|---|---|
| Id | Model identifier in ASMS | |
| Reference | Unique identifier to create a relationship between the concepts project > category, itemType, typeRegister, applicant, responsibleGroup, responsible, company, client | see |
| state | Relationship of ASMS and DevOps state values | see |
| additionalFields | Relationship of additional fields between ASMS and DevOps fields | See |
Relación de los estados
To relate the states, the integration provides the following json schema:
{
"value": "",
"id": 0,
"reason": 0,
"commentary": {
"value": "",
"Key": ""
}
}
Where:
| Property | Description |
|---|---|
| value | State identifier in DevOps DevOps states |
| Id | Status Identifier in ASMS |
| reason | Status Change Reason Identifier in ASMS |
| commentary | Relates the solution field of the ticket in ASMS to an equivalent field in DevOps; where “key” is the identifier of the field in DevOps; if the property “key” is null can assign a default value using “value”. |
EXAMPLE: ASMS/DevOps Status Ratio
To create the list of states, follow the instructions below:
- Get the IDs of ASMS states.
- Get the IDs of DevOps states.
- Assign the following status equivalence:
- The property commentary (Represents the “Case Solution” in ASMS), we relate it to an equivalent field in DevOps for the example we will use the name close_case.
| DevOps Status | State in Aranda | Id State Aranda | Value state DevOps |
|---|---|---|---|
| New | NEW | 1 | value_new |
| Closed | CLOSED | 13 | value_closed |
- Type the Id State Aranda On Property “id” and the Value state DevOps of its equivalent taken from DevOps On Property value:
[
{
"id": 1,
"value": "value_new",
"commentary": {
"Key": "close_case"
}
},
{
"id": 13,
"value": "value_closed",
"commentary": {
"Key": "close_case"
}
}
]
Relación entre los campos adicionales y los campos de las clases de DevOps
The relationship between the additional fields and the equivalent DevOps fields is done using the following JSON structure:
additionalFields internal properties
{
"id": 0,
"field": {
"key": ""
},
"value": [
""
],
"mapping": [
{
"id": 0,
"value": ""
}
]
}
Where:
| Properties | Description | |
|---|---|---|
| Id | Additional field identifier in ASMS | |
| value | Allows you to add values to additional fields as constant values | |
| field | DevOps Field Information | see |
| mapping | Relationship of values for ASMS and DevOps fields, where “id” is the identifier in ASMS and “value” is the identifier in DevOps |
Listado de los tipos de campo adicionales soportados
Listado de relación entre los tipos de campos de las plataformas:
| ASMS | Field Name/Label in DevOps | Restrictions |
|---|---|---|
| Short Text | Text (single line) | |
| Paragraph | Text (multiple lines) | |
| Date | Date/TimeDate | |
| Date and Time | Date/Time | |
| Numeric | Integer | DevOps does not support supports values greater than 32 bytes (2147483647) |
| Decimal | Decimal | |
| List | Picklist (string) - Picklist (integer) | |
| Link | Text (single line) | |
| Catalog (List) | Picklist (string) - Picklist (integer) | |
| True/false | They boan | |
| URL | Text (multiple lines) |
⚐ Note: Associating 2 different fields to those listed in the previous table results in a runtime error