Continuing with the file configuration you must record a relationship between the fields of the ASMS task with the fields of the Jira Server sub-task.
The relationship between ASMS and Jira Server task fields is presented by the following JSON (Configuration File):
{
"task": [
{
"reference": "",
"definition": {
"idByProject": {
"type": "",
"key": ""
},
"subject": {
"type": "",
"key": ""
},
"description": {
"type": "",
"key": ""
},
"responsible": {
"type": "",
"key": "",
"SearchBy": [""]
},
"responsibleGroup": {
"key": "",
"type": "",
"defaultValue": {
"id": 0,
"value": ""
}
},
"duration": {
"type": "",
"key": ""
},
"enddate": {
"type": "",
"key": ""
},
"startdate": {
"type": "",
"key": ""
}
},
"model": {
"id": 0,
"additionalFields": [
{
"id": 0,
"type": "",
"field": {
"key": ""
},
"mapping": [
{
"id": 0,
"value": ""
},
{
"id": 0,
"value": ""
},
{
"id": 0,
"value": ""
}
]
}
],
"state": [
{
"id": 0,
"value": "",
"reason": 0,
"commentary": {
"key": "",
"value": ""
}
}
]
}
}
]
}
1. On the property “reference” in the configuration file type the “key” that he registered in The previous section; Duplicates of this property are not supported:
{
"task": [
{
"reference": "project 1",
"definition": {
"subject": {
},
"description": {
},
"idByProject": {
},
"responsibleGroup": {
},
"responsible": {
},
"duration": {
},
"enddate": {
},
"startdate": {
}
}
}
]
}
2. Get the name of the Jira Server properties that you will relate to the ASMS properties, see Jira Server Properties:
| Ownership in Jira Server | Jira Property ID |
|---|---|
| Title | Summary |
| Description | Description |
| idByProject | customfield_10293 |
| Responsible | assignee |
| Responsible Group | customfield_10041 |
| Duration | customfield_10294 |
| End up | customfield_10295 |
| startdate | customfield_10296 |
3. Create a relationship between ASMS properties and Jira Server:
| Property in ASMS | Ownership in Jira Server |
|---|---|
| subject | Summary |
| Description | Description |
| state | state * |
| responsible | assignee |
| responsibleGroup | customfield_10041 |
| Duration | customfield_10294 |
| Finish it | customfield_10295 |
| initialdate | customfield_10296 |
| idByProject | customfield_10293 |
⚐ Note: Fields assigned with an asterisk ( * ) are assigned internally and cannot be modified.
4. Assign the type of mapping that the properties will perform:
| Name | Description |
|---|---|
| Value | Allows you to assign a value to the selected field through the configuration file. The value is required to be within the value ratio properties |
| Mapper | Seeks to associate and/or relate the values of the Aranda task with the values of the associated field of Jira Server, the relationship of values is made 1 to 1, the assignment is not allowed to be repeated |
| FieldValue | Property values are sent directly between platforms without any association/relationship |
Field Relationship
| Property in ASMS | Ownership in Jira Server | Mapping Type |
|---|---|---|
| subject | Summary | FieldValue |
| Description | Description | FieldValue |
| state | state * | - |
| responsible | assignee | Mapper |
| responsibleGroup | customfield_10041 | Mapper |
| Duration | customfield_10294 | FieldValue |
| Finish it | customfield_10295 | FieldValue |
| initialdate | customfield_10296 | FieldValue |
| idByProject | customfield_10293 | FieldValue |
⚐ Note: Properties without any mapping will be covered in another section.
5. For this setting, defaults are set for the “responsible”, this value will be added if the “Responsible” of Jira to Asms or Asms to Jira is not found.
6. Consult the ID of the Responsible in Asms that you will assign by default.
7. Check the Responsible Person ID in Jira that you will assign by default Jira Server Users.
8. In internal ownership “defaultValue” of “responsible”, add the ID of the Responsible queried in point 8 in the property **“id” of defaultValue, for the example 3 will be used.
9. In internal ownership “defaultValue” of “responsible”, add the ID of the Responsible queried in point 9 in the property “value” defaultValue, the example will use user373.
10. Type the relationship defined in the previous steps in the configuration file:
{
"defaultValue": {
"id": 3,
"value": "user373"
}
}
11. Type in the configuration file the relationship created for the property’s defaults “responsible”:
{
"responsible": {
"type": "Mapper",
"key": "assignee",
"defaultValue": {
"id": 3,
"value": "user373"
}
}
}
12. Replicate the steps for each definition and according to the client’s needs
{
"task": [
"reference": "project 1",
"definition": {
"idByProject": {
"type": "FieldValue",
"key": "customfield_10293"
},
"subject": {
"type": "FieldValue",
"key": "summary"
},
"description": {
"type": "FieldValue",
"key": "description"
},
"responsible": {
"type": "FieldValue",
"key": "assignee",
"SearchBy":["Email"],
"defaultValue": {
"id": 3,
"value": "user373"
}
},
"responsibleGroup": {
"key": "customfield_10041",
"type": "Mapper"
},
"duration": {
"type": "FieldValue",
"key": "customfield_10294"
},
"enddate": {
"type": "FieldValue",
"key": "customfield_10295"
},
"startdate": {
"type": "FieldValue",
"key": "customfield_10296"
}
}
]
}
Continue: Register the “Mapping” property (step 4) ↪