Relationship of additional states and fields with Jira Server Issue properties
The relationship of the states between the platforms and the additional fields is represented by the following JSON:
{
"model": [
{
"reference": "",
"id": 0,
"state": [
{
"value": "",
"id": 0,
"reason": 0,
"commentary": {
"Key": "",
"value": ""
}
}
],
"additionalFields": [
{
"id": 0,
"field": {
"key": ""
},
"value": [
""
],
"mapping": [
{
"id": 0,
"value": ""
}
]
}
]
}
]
}
Where:
Properties
| Properties | Description | |
|---|---|---|
| Id | Model identifier in ASMS | |
| Reference | Unique identifier to create a relationship between the concepts project > category, itemType, typeRegister, applicant, responsibleGroup, responsible, company, client | see |
| state | Relationship of ASMS and Jira Server status values | See |
| additionalFields | Relationship of additional fields between ASMS and Jira Server fields | See |
Relación de los estados
To relate the states, the integration provides the following json schema:
{
"value": "",
"id": 0,
"reason": 0,
"commentary": {
"value": "",
"Key": ""
}
}
Where:
| Property | Description |
|---|---|
| value | Status ID in Jira Server Jira Server Statuses |
| Id | Status Identifier in ASMS |
| reason | Status Change Reason Identifier in ASMS |
| commentary | Relates the ticket solution field in ASMS to an equivalent field in Jira Server; where “key” is the identifier of the field in Jira Server; if the property “key” is null can assign a default value using “value”. |
EXAMPLE: ASMS/Jira Server Status Ratio
To create the list of states, follow the instructions below:
- Get the IDs of ASMS states.
- Get the IDs of the Jira Server states.
- Assign the following status equivalence:
- The property commentary (Represents the “Case Solution” in ASMS), we relate it to an equivalent field in Jira Server for the example we will use the name close_case.
| Status on Jira Server | State in Aranda | Id State Aranda | Value state Jira Server |
|---|---|---|---|
| New | NEW | 1 | value_new |
| Closed | CLOSED | 13 | value_closed |
- Type the Id State Aranda On Property “id” and the Value state Jira Server of its equivalent taken from Jira Server On Property value:
[
{
"id": 1,
"value": "value_new",
"commentary": {
"Key": "close_case"
}
},
{
"id": 13,
"value": "value_closed",
"commentary": {
"Key": "close_case"
}
}
]
Relación entre los campos adicionales y los campos de las clases de Jira Server
The relationship between the additional fields and the equivalent fields in Jira Server is done using the following JSON structure:
additionalFields internal properties
{
"id": 0,
"field": {
"key": "",
},
"value":[
""
],
"mapping": [
{
"id": 0,
"value": ""
}
]
}
Where:
| Properties | Description | |
|---|---|---|
| Id | Additional field identifier in ASMS | |
| value | Allows you to add values to additional fields as constant values | |
| field | Jira Server Field Information | see |
| mapping | Value relationship for ASMS and Jira Server fields, where “id” is the identifier in ASMS and “value” is the identifier in Jira Server |
Listado de los tipos de campo adicionales soportados
Listado de relación entre los tipos de campos de las plataformas:
| ASMS | Field ID in Jira Server | Field Name/Label in Jira Server |
|---|---|---|
| Short Text | com.atlassian.jira.plugin.system.customfieldtypes:textfield | Short text |
| Paragraph | com.atlassian.jira.plugin.system.customfieldtypes:textarea | Paragraph |
| Date | com.atlassian.jira.plugin.system.customfieldtypes:datepicker | Date |
| Date and Time | com.atlassian.jira.plugin.system.customfieldtypes:datetime | Timestamp |
| Numeric | com.atlassian.jira.plugin.system.customfieldtypes:float | Number |
| Decimal | com.atlassian.jira.plugin.system.customfieldtypes:float | Number |
| List | com.atlassian.jira.plugin.system.customfieldtypes:select | Drop-down menu |
| Link | com.atlassian.jira.plugin.system.customfieldtypes:url | URL |
| Catalog (List) | com.atlassian.jira.plugin.system.customfieldtypes:select | Drop-down menu |
⚐ Note: Associating 2 different fields to those listed in the previous table results in a runtime error