Relationship of additional states and fields with the properties of Jira Server sub-tasks
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 | Task Model Identifier in ASMS | |
| Reference | Unique identifier to create a relationship between tasks per model | |
| state | Relationship of task status values in ASMS and sub-task in Jira Server | See |
| additionalFields | Relationship of the additional fields between the task in ASMS and the sub-task fields in Jira Server | See |
List of states
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 task 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 statement list, consider the following instructions:
- Get the IDs of the task statuses in ASMS.
- Get the Ids of the sub-task statuses in Jira Server.
- Assign the following status equivalence:
- The property commentary (Represents the “Task Solution” in ASMS), we relate it to an equivalent field in Jira Server for the example we will use the name close_task.
| 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_task"
}
},
{
"id": 13,
"value": "value_closed",
"commentary": {
"Key": "close_task"
}
}
]
Relationship between additional fields and fields in Jira Server subtasks
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,
"type": "FIELDVALUE/MAPPING/VALUE",
"field": {
"key": ""
},
"value": [
""
],
"mapping": [
{
"id": 0,
"value": ""
}
]
}
Where:
| Properties | Description | |
|---|---|---|
| Id | Additional field identifier in ASMS | |
| type | You can choose between (FIELDVALUE/MAPPING/VALUE) to specify the behavior of the integration between each additional field | see |
| 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 |
type
| Properties | Description |
|---|---|
| FIELDVALUE | Direct relationship between tool fields, taking into account the list of additional supported fields |
| MAPPING | Relationship by means of value mapping |
| VALUE | Add consistent value to fields |
List of additional supported field types
List of relationship between the types of fields of the platforms:
| ASMS | Field ID in Jira Server | Field Name/Label in Jira Server |
|---|---|---|
| Short Text | com.atlassian.jira.plugin.system.customfieldtypes:textfield | Short text (plain text only) |
| Paragraph | com.atlassian.jira.plugin.system.customfieldtypes:textarea | Paragraph (supports rich text) |
| Date | com.atlassian.jira.plugin.system.customfieldtypes:datepicker | Date picker |
| Date and Time | com.atlassian.jira.plugin.system.customfieldtypes:datetime | Date and time picker |
| Numeric | com.atlassian.jira.plugin.system.customfieldtypes:float | Numeric field |
| Decimal | com.atlassian.jira.plugin.system.customfieldtypes:float | Numeric field |
| List | com.atlassian.jira.plugin.system.customfieldtypes:select | Selection list (individual option) |
| Link | com.atlassian.jira.plugin.system.customfieldtypes:url | URL field |
| Catalog (List) | com.atlassian.jira.plugin.system.customfieldtypes:select | Selection list (individual option) |
| Catalog (List) | com.atlassian.jira.plugin.system.customfieldtypes:cascadingselect | Picklist (Cascade) |
⚐ Notes: Associating 2 different fields to those listed in the previous table results in a runtime error
- For the picklist (waterfall) field, only one level is supported as currently allowed by Jira, i.e. parent and child
- Currently the relationship type allowed for these fields is of type FieldValue