Continuing with the file configuration, a relationship between the fields in the ASMS case and the fields in the DevOps WorkItem must be recorded.
The relationship between ASMS and DevOps case fields is presented using the following JSON (Configuration File):
{
"case": [
{
"reference": "",
"definition": {
"subject": {
"type": "",
"key": ""
},
"description": {
"type": "",
"key": ""
},
"idByProject": {
"type": "",
"key": ""
},
"responsible": {
"type": "",
"key": "",
"searchBy": [ "" ],
"defaultValue": {
"id": 0,
"value": ""
}
},
"responsibleGroup": {
"key": "",
"type": "",
"defaultValue": {
"id": 0,
"value": ""
}
},
"client": {
"type": "",
"key": "",
"searchBy": [ "" ],
"defaultValue": {
"id": 0,
"value": ""
}
},
"company": {
"type": "",
"key": "",
"defaultValue": {
"id": 0,
"value": ""
}
},
"applicant": {
"type": "",
"key": "",
"searchBy": [ "" ],
"defaultValue": {
"id": 0,
"value": ""
}
},
"typeRegister": {
"type": "",
"key": "",
"defaultValue": {
"id": 0,
"value": ""
}
},
"ci": {
"type": "",
"key": "",
"defaultValue": {
"id": 0,
"value": ""
}
}
}
}
],
"urgency": [
],
"impact": [
],
"model": [
],
"typeRegister": [
],
"project": [
],
"category": [
],
"applicant": [
],
"responsibleGroup": [
],
"responsible": [
],
"ci": [
]
}
1. On the property “reference” in the configuration file type the “key” that he registered in The previous section; Duplicates of this property are not supported:
{
"case": [
{
"reference": "project 1",
"definition": {
"subject": {
},
"description": {
},
"idByProject":{
},
"typeRegister": {
},
"applicant": {
},
"responsibleGroup": {
},
"responsible": {
},
"client": {
},
"company": {
}
}
}
]
}
2. Get the name of the DevOps properties that you will relate to the ASMS properties, see DevOps Properties:
| DevOps Property | DevOps Property ID |
|---|---|
| Title | System.Title |
| Description | System.Description |
| State | System.State |
| Responsible | System.AssignedTo |
| Record Type | Custom.recordtype |
| User Group | Custom.usergroup |
| Customer | Custom.client |
| Company | Custom.company |
| Applicant | Custom.applicant |
| CI | Custom.CI |
| Case Id | Custom.CaseId |
3. Create a relationship between ASMS and DevOps properties:
| Property in ASMS | DevOps Property |
|---|---|
| subject | System.Title |
| Description | System.Description |
| state | System.State * |
| responsible | System.AssignedTo |
| typeRegister | Custom.recordtype |
| responsibleGroup | Custom.usergroup |
| client | Custom.client |
| Company | Custom.company |
| applicant | Custom.applicant |
| Ci | Custom.CI |
| idByProject | Custom.CaseId |
⚐ Note: Fields assigned with an asterisk ( * ) are assigned internally and cannot be modified.
4. Assign the type of mapping that the properties will perform:
| Name | Description |
|---|---|
| Value | Allows you to assign a value to the selected field through the configuration file. The value is required to be within the value ratio properties |
| Mapper | It seeks to associate and/or relate the values of the Aranda case with the values of the associated DevOps field, the relationship of values is made 1 to 1, the assignment is not allowed to be repeated |
| FieldValue | Property values are sent directly between platforms without any association/relationship |
Field Relationship
| Property in ASMS | DevOps Property | Mapping Type |
|---|---|---|
| subject | System.Title | FieldValue |
| Description | System.Description | FieldValue |
| state | System.State * | - |
| responsible | System.AssignedTo | Mapper |
| typeRegister | Custom.recordtype | Mapper |
| responsibleGroup | Custom.usergroup | FieldValue |
| client | Custom.client | Mapper |
| Company | Custom.company | Mapper |
| applicant | Custom.applicant | FieldValue |
| Ci | Custom.CI | FieldValue |
| idByProject | Custom.CaseId | FieldValue |
⚐ Note: Properties without any mapping will be covered in another section.
5. For this setting, defaults are set for the “responsible”, this value will be added if the “Responsible” from DevOps to Asms or Asms to DevOps is not found.
6. Consult the ID of the Responsible in Asms that you will assign by default.
7. Consult the ID of the Responsible in DevOps that you will assign by default, remember that the ID of the user in DevOps is the email with which you registered.
8. In internal ownership “defaultValue” of “responsible”, add the ID of the Responsible queried in point 6 in the “id” defaultValue for example 3.
9. In internal ownership “defaultValue” of “responsible”, add the ID of the Responsible queried in point 7 in the property “value” of defaultValue, for the example we will use user1@aranda.com.
10. Type the relationship defined in the previous steps in the configuration file:
{
"defaultValue": {
"id": 3,
"value": "user1@aranda.com"
}
}
11.Optional tag “searchBy” is added for the definition of the “applicant” property
{
"applicant": {
"type": "FieldValue",
"key": "Custom.applicant",
"searchBy": [ "Email" ]
}
}
12. Type in the configuration file, the relationship created for the default values of the property “responsible”:
{
"case": [
{
"reference": "project 1",
"definition": {
"subject": {
"type": "FieldValue",
"key": "System.Title"
},
"description": {
"type": "FieldValue",
"key": "System.Description"
},
"responsible": {
"type": "Mapper",
"key": "System.AssignedTo",
"defaultValue": {
"id": 3,
"value": "user1@aranda.com"
}
},
"responsibleGroup": {
"key": "Custom.grupodeusuarios",
"type": "FieldValue"
},
"client": {
"type": "Mapper",
"key": "Custom.cliente"
},
"company": {
"type": "Mapper",
"key": "Custom.company"
},
"applicant": {
"type": "FieldValue",
"key": "Custom.applicant",
"searchBy": [ "Email" ]
},
"typeRegister": {
"type": "Value",
"key": "Custom.tipoderegistro"
},
"ci": {
"type": "FieldValue",
"key": "Custom.CI"
}
}
}
]
}