Relationship between the Category and the Jira Server project
The integration requires relating the Service Project > Category > the Jira Server project, the following json schema allows us to create this relationship:
{
"project": [
{
"id": 0,
"service": 0,
"category": [
{
"reference": "",
"id": 0,
"value": ""
}
]
}
]
}
Where
| Properties | Description |
|---|---|
| Id | Aranda ASMS Project Identifier |
| service | Identifier of the service to which the Jira Server Issue will be associated |
| category | Represents the relationship of the category to the Jira Server project Relationship of the category to the Jira Server project |
Relationship of the category to the Jira Server project
To relate the categories, integration provides the following json schema:
{
"category": [
{
"reference": "",
"id": 0,
"value": ""
}
]
}
Where:
| Properties | Description |
|---|---|
| Reference | Unique identifier to create a relationship between the concepts project > category, itemType, typeRegister, applicant, responsibleGroup, responsible, company, client see |
| value | Jira Server Project ID Jira Server Project |
| Id | Category identifier in ASMS |
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 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 truth and allows the system to create and update tickets in ASMS. The Aranda CMDB can only update tickets on the Jira Cloud platform |