Relationship between the Category and the DevOps project
The integration requires relating the Service Project » Category with the DevOps project, the following json schema allows us to create this relationship:
{
"project": [
{
"id": 0,
"collection": "",
"service": null,
"category": [
{
"reference": "",
"id": 0,
"project": "",
"dataSource": ""
}
]
}
]
}
Where
| Properties | Description |
|---|---|
| Id | Aranda ASMS Project Identifier |
| Collection | Collection/Organization Name in DevOps |
| service | Identifier of the service to which the DevOps WorkItem will be associated |
| category | Represents the relationship of the category to the DevOps project Relationship of the category to the DevOps project |
Relationship of the category to the DevOps project
To relate the categories, integration provides the following json schema:
{
"category": [
{
"dataSource": "",
"reference": "",
"id": 0,
"project": ""
}
]
}
Where:
| Properties | Description |
|---|---|
| Id | Category identifier in ASMS |
| dataSource | Determine the platform that will create the tickets, see |
| Reference | Unique identifier to create a relationship between the concepts project > category, itemType, typeRegister, applicant, responsibleGroup, responsible, company, client see |
| Project | DevOps Project ID DevOps Project |
Allowed values for dataSource
The property “dataSource” allows the integration to determine which platform will be the source of information, by default its value is “Aranda”:
| Name | Description |
|---|---|
| Both | Both platforms can create and update tickets |
| Aranda | ASMS acts as the source of truth and allows the system to create and update tickets in the DevOps platform. The DevOps platform is only allowed to update tickets in ASMS |
| External | The DevOps platform acts as the source of truth and allows the system to create and update tickets in ASMS. The Aranda CMDB can only update tickets in the DevOps platform |