Relationship of additional states and fields to Jira Cloud 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

List of states

To relate the states, the integration provides the following json schema:

{
  "value": "",
  "id": 0,
  "reason": 0,
  "commentary": {
      "value": "",
      "Key": ""
  }
}

Where:

EXAMPLE: ASMS / Jira Cloud Status Ratio

To create the list of states, follow the instructions below:

1. Get the IDs of ASMS states.
2. Get the IDs of Jira Cloud statuses.
3. Assign the following status equivalence:
4. The property commentary (Represents the “Case Solution” in ASMS), we relate it to an equivalent field in Jira Cloud for the example we will use the name close_case.

• Type the Id State Aranda On Property “id” and the Value state Jira CLoud of its equivalent taken from Jira Cloud On Property value:

[
  {
      "id": 1,
      "value": "value_new",
      "commentary": {
      "Key": "close_case"
      }
  },
  {
      "id": 13,
      "value": "value_closed",
      "commentary": {
      "Key": "close_case"
      }
  }
]

Relationship between additional fields and fields in Jira Cloud classes

The relationship between the additional fields and the equivalent fields in Jira CLoud is done using the following JSON structure:

additionalFields internal properties

{
  "id": 0,
  "type": "FIELDVALUE/MAPPING/VALUE",
  "field": {
    "key": ""
  },
  "value": [
    ""
  ],
  "mapping": [
    {
      "id": 0,
      "value": ""
    }
  ]
}

Where:

type

List of additional supported field types

List of relationship between the types of fields of the platforms:

⚐ 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

↩ Back to Settings