Register the "case" property | Aranda Integration Center

Continuing with the configuration of the file, a relationship must be recorded between the fields of the ASMS case with the fields of the Jira Server issue.

The relationship between ASMS and Jira Server case fields is presented by the following JSON (Configuration File):

{
  "case": [
    {
      "reference": "",
      "definition": {
        "subject": {
          "type": "",
          "key": ""
        },
        "description": {
          "type": "",
          "key": ""
        },
        "responsible": {
          "type": "",
          "key": "",
          "defaultValue": {
            "id": 0,
            "value": ""
          }
        },
        "responsibleGroup": {
          "key": "",
          "type": "",
          "defaultValue": {
            "id": 0,
            "value": ""
          }
        },
        "client": {
          "type": "",
          "key": "",
          "defaultValue": {
            "id": 0,
            "value": ""
          }
        },
        "company": {
          "type": "",
          "key": "",
          "defaultValue": {
            "id": 0,
            "value": ""
          }
        },
        "applicant": {
          "type": "",
          "key": "",
          "defaultValue": {
            "id": 0,
            "value": ""
          }
        },
        "typeRegister": {
          "type": "",
          "key": "",
          "defaultValue": {
            "id": 0,
            "value": ""
          }
        },
        "ci": {
          "type": "",
          "key": "",
          "defaultValue": {
            "id": 0,
            "value": ""
          }
        }
      }
    }
  ],
  "urgency": [
  ],
  "impact": [
  ],
  "model": [
  ],
  "typeRegister": [
  ],
  "project": [
  ],
  "category": [
  ],
  "applicant": [
  ],
  "responsibleGroup": [
  ],
  "responsible": [
  ]
}

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:

{
  "case": [
    {
      "reference": "project 1",
      "externalIdField": "",
      "definition": {
        "subject": {
        },
        "description": {
        },
        "typeRegister": {
        },
        "applicant": {
        },
        "responsibleGroup": {
        },
        "responsible": {
        },
        "client": {
        },
        "company": {
        },
        "ci": {
        }
      }
    }
  ]
}

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
Label	Name
Description	Description
State	state
Responsible	assignee
Title	Summary
Type Register	customfield_10123
Responsible Group	customfield_10119
Client	customfield_10120
Company	customfield_10121
Applicant	customfield_10122
Ci	customfield_10124

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
typeRegister	customfield_10123
responsibleGroup	customfield_10119
client	customfield_10120
Company	customfield_10121
applicant	customfield_10122
Ci	customfield_10124

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 case 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
typeRegister	customfield_10123	Mapper
responsibleGroup	customfield_10119	FieldValue
client	customfield_10120	Mapper
Company	customfield_10121	Mapper
applicant	customfield_10122	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 we will use 3.

9. In internal ownership “defaultValue” of “responsible”, add the ID of the Responsible queried in point 9 in the property “value” defaultValue, for the example we’ll 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”:

{
  "case": [
    {
      "reference": "project 1",
      "definition": {
        "subject": {
          "type": "FieldValue",
          "key": "summary"
        },
        "description": {
          "type": "FieldValue",
          "key": "Description"
        },
        "responsible": {
          "type": "Mapper",
          "key": "assignee",
          "defaultValue": {
            "id": 3,
            "value": "user373"
          }
        },
        "responsibleGroup": {
          "key": "customfield_10119",
          "type": "FieldValue"
        },
        "client": {
          "type": "Mapper",
          "key": "customfield_10120"
        },
        "company": {
          "type": "Mapper",
          "key": "customfield_10121"
        },
        "applicant": {
          "type": "FieldValue",
          "key": "customfield_10122"
        },
        "typeRegister": {
          "type": "Value",
          "key": "customfield_10123"
        },
        "ci": {
          "type": "FieldValue",
          "key": "customfield_10124"
        }
      }
    }
  ]
}

Continue: Register the “Mapping” property (step 3) ↪

↩ Return