Relationship between Category and Jira Cloud project
The integration requires relating the Service Project > Category > the Jira Cloud project, the following json schema allows us to create this relationship:
{
"project": [
{
"id": 0,
"service": 0,
"category": [
{
"reference": "",
"dataSource": "",
"id": 0,
"value": ""
}
]
}
]
}
Where
| Properties | Description |
|---|---|
| Id | Aranda ASMS Project Identifier |
| service | Identifier of the service to which the Jira Cloud Issue will be associated |
| category | Represents the relationship of the category to the Jira Cloud project Relationship of the category to the Jira Cloud project |
Relación de la categoría con el proyecto de Jira Cloud
Para relacionar las categorías la integración proporciona el siguiente esquema json:
{
"category": [
{
"dataSource": "",
"reference": "",
"id": 0,
"value": ""
}
]
}
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 |
| value | Jira Cloud Project ID Jira Cloud Project |
Valores permitidos para 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 information and allows the system to create and update tickets on the Jira CLoud platform. The Jira Cloud platform is only allowed to update tickets in ASMS |
| External | The Jira CLoud platform acts as the source of information and allows the system to create and update tickets in ASMS. The Aranda CMDB can only update tickets on the Jira CLoud platform |