The property “model” relates the States and Additional ASMS Fields, the configuration file has the following JSON for model:
{
"model": [
{
"id": 0,
"reference": "",
"state": [
{
"value": "",
"id": 0,
"commentary": {
"Key": "",
"value": ""
}
}
],
"additionalFields": [
{
"id": 0,
"field": {
"key": ""
},
"mapping": [
{
"id": 0,
"value": ""
}
]
}
]
}
]
}
1. With the help of a Aranda Service Management (ASMS) get the model ID using the Project, Service, and Category IDs obtained in The previous section, this value will be recorded in the model.id in the configuration file.
Choose the model you will use for the integration, with the help of an Aranda Service Management (ASMS) administrator obtain the model ID associated with the project, service and category, previously assigned.
2. Type the values in the “model.id” from the configuration file:
{
"model": [
{
"id": 15,
"state": [
],
"additionalFields": [
]
}
]
}
Note: No need to register the property “reference” of “model” because only one category was registered.
Case Statuses
3. With the help of a Aranda Service Management (ASMS) get the IDs of the States of the case.
4. The property State ASMS relates to ownership Status of Jira Cloud, this relationship cannot be modified and/or related to another property of the Jira Issue.
5. Get the values for the property Status Jira Cloud section, as taught in the “Register model”, you will find an example of how to check these statuses.
6. Establish an equivalence between the values for the States as follows:
| Status JiraCloud | ASMS Record Type | ID ASMS Record Type | VALUE Status JiraCloud |
|---|---|---|---|
| New | New | 187 | 1 |
| In Progress | In Progress | 188 | 2 |
| On Hold | On Hold | 189 | 3 |
| Resolved | Resolved | 190 | 5 |
| Closed | Closed | 191 | 6 |
7. Type the values in the “model.state” from the configuration file:
{
"model": [
{
"state": [
{
"value": "1",
"id": 187
},
{
"value": "2",
"id": 188
},
{
"value": "3",
"id": 189
},
{
"value": "5",
"id": 190
},
{
"value": "6",
"id": 191
}
],
"id": 15,
"additionalFields": [
]
}
]
}
Solution
8. In ASMS by configuration cases require the “Solution” property to have a value, this solution is determined by the state in which the case is located.
To solve this requirement, the configuration file allows you to add a value statically or obtain it directly from Jira CLoud, using the following property:
{
"commentary": {
"key": "",
"value": ""
}
}
Where:
“key”: name of the Jira Cloud property where the solution will be obtained. “value”: static value to be assigned to the ASMS solution.
9. Assign a Jira Cloud field that you will relate to the ASMS “Solution” field
10. Type in the configuration file the relationship of the ASMS solution field to the Jira Cloud field.
Keep in mind that not all states require a solution, it depends on the configuration of the platforms.
{
"model": [
{
"state": [
{
"value": "1",
"id": 187
},
{
"value": "2",
"id": 188
},
{
"value": "3",
"id": 189,
"commentary": {
"Key": "close_notes"
}
},
{
"value": "5",
"id": 190,
"commentary": {
"Key": "close_notes"
}
},
{
"value": "6",
"id": 191,
"commentary": {
"Key": "close_notes"
}
}
],
"id": 15,
"additionalFields": [
]
}
]
}
Additional fields
11. In ASMS and Jira Cloud the creation of additional fields is allowed, if you want to include some of them in the integration follow the instructions below.
12. We recommend that you create a table with the fields you want to add in the integration as follows:
| field in Jira Cloud | field in ASMS | Jira Cloud field id | Id ASMS field |
|---|---|---|---|
| Fixed field | Fixed field | u_campo_fijo | 286 |
| Short text | Short text | u_texto_corto | 287 |
| towns | towns | u_glide_list | 288 |
| Configuration Item | Configuration Item | u_reference_12 | 298 |
13. Choose the type of integration to which each field is going to be related: FIELDVALUE, VALUE or MAPPING and write the information in the json file.
The value property is only required when constant values are desired.
{
"model": [
{
"id": 15,
"state": [
{
"value": "1",
"id": 187
},
{
"value": "2",
"id": 188
},
{
"value": "3",
"id": 189,
"commentary": {
"Key": "close_notes"
}
},
{
"value": "5",
"id": 190,
"commentary": {
"Key": "close_notes"
}
},
{
"value": "6",
"id": 191,
"commentary": {
"Key": "close_notes"
}
}
],
"additionalFields": [
{
"type": "VALUE",
"id": 286,
"value": "un valor que quiero que sea constante",
"field": {
"key": "u_campo_fijo"
}
},
{
"type": "FIELDVALUE",
"id": 287,
"field": {
"key": "u_texto_corto"
}
},
{
"type": "MAPPING",
"id": 288,
"field": {
"key": "u_glide_list"
}
},
{
"type": "FIELDVALUE",
"id": 298,
"field": {
"key": "u_reference_12"
}
}
]
}
]
}
14. To complete the configuration in the MAPPING types, you have to add the mapping property.
15. To complete the configuration of the MAPPING type, list the ids of the values in ASMS and Jira Cloud and write them in the mapping property, where id is the identifier of the value of the list in ASMS and value in the identifier of the value in the Jira Cloud list.
Example for a list of values of the Mapping, with the help of an ASMS administrator, identify the IDs of each value of the additional field in ASMS and the IDs of each value of the additional field in Jira Cloud:
| field in Jira Cloud | field in ASMS | Id value Jira Cloud | Id value ASMS |
|---|---|---|---|
| Countries | Countries | 10100 | 35 |
| Countries | Countries | 10101 | 34 |
{
"model": [
{
"id": 15,
"state": [
{
"value": "1",
"id": 187
},
{
"value": "2",
"id": 188
},
{
"value": "3",
"id": 189,
"commentary": {
"Key": "close_notes"
}
},
{
"value": "5",
"id": 190,
"commentary": {
"Key": "close_notes"
}
},
{
"value": "6",
"id": 191,
"commentary": {
"Key": "close_notes"
}
}
],
"additionalFields": [
{
"type": "VALUE",
"id": 286,
"value": "un valor que quiero que sea constante",
"field": {
"key": "u_campo_fijo"
}
},
{
"type": "FIELDVALUE",
"id": 287,
"field": {
"key": "u_texto_corto"
}
},
{
"type": "MAPPING",
"id": 288,
"field": {
"key": "u_glide_list"
},
"mapping": [
{
"id": 35,
"value": "10100"
},
{
"id": 34,
"value": "10101"
}
]
},
{
"type": "FIELDVALUE",
"id": 298,
"field": {
"key": "u_reference_12"
}
}
]
}
]
}
Continue: Register the “Urgency” property (step 5) ↪