EN
Español
English
Português
    Integration scenarios

    The Aranda Service Desk (ASMS) integration with Jira Cloud contemplates the following scenarios for configuration file configuration

    A model associated with multiple categories and these associated with a Jira project

    • No ownership required Reference on the model property.
    • All categories are associated with the same project, for this reason it only requires a definition in the “case”.
    • If the model associated with the service, category, or case type is not registered, it generates a run-time error.
    {
  "project": [
    {
      "id": 1,
      "service": 2,
      "category": [
        {
          "reference": "ref 1",
          "id": 1,
          "value": "proyecto 1"
        },
        {
          "reference": "ref 1",
          "id": 2,
          "value": "proyecto 1"
        },
        {
          "reference": "ref 1",
          "id": 3,
          "value": "proyecto 1"
        }
      ]
    }
  ],
  "itemType": [
    {
      "reference": "ref 1",
      "type": "ServiceCall",
      "workItemType": "Feature"
    },
    {
      "reference": "ref 1",
      "type": "Problem",
      "workItemType": "Bug"
    }
  ],
  "case": [
    {
      "reference": "ref 1",
      "definition": {
      }
    }
  ],
  "model": [
    {
      "id": 1,
      "state": [
      ]
    }
  ]
}

    A model associated with multiple categories and these associated with a Jira project with different definitions (fields for each type of case) of the Jira project

    Three categories associated with a case type (ServiceCall) are registered, generating the following association:

    Category Case Type Model Jira Project
    1 ServiceCall 1 Project 1
    2 ServiceCall 1 Project 1
    3 ServiceCall 1 Project 1
    • If the model associated with the service, category, or case type is not registered, it generates a run-time error

    In Jira each type of issue has custom fields, the configuration file must allow the relationship of the ASMS fields with the Jira fields so we will relate the property “case” and “model” through property “reference”

    Category Case Type Model Jira Project case (reference) model (reference)
    1 ServiceCall 1 Project 1 ref 1 ref 1
    2 ServiceCall 1 Project 1 ref 2 ref 2
    3 ServiceCall 1 Project 1 Ref 3 Ref 3
    • No ownership required Reference in the model property, because all categories belong to the same model.
    {
  "project": [
    {
      "id": 1,
      "service": 2,
      "category": [
        {
          "reference": "ref 1",
          "id": 1,
          "value": "proyecto 1"
        },
        {
          "reference": "ref 2",
          "id": 2,
          "value": "proyecto 1"
        },
        {
          "reference": "ref 3",
          "id": 3,
          "value": "proyecto 1"
        }
      ]
    }
  ],
  "itemType": [
    {
      "reference": "ref 1",
      "type": "ServiceCall",
      "workItemType": "Feature"
    },
    {
      "reference": "ref 2",
      "type": "ServiceCall",
      "workItemType": "Feature"
    },
    {
      "reference": "ref 3",
      "type": "ServiceCall",
      "workItemType": "Feature"
    }
  ],
  "case": [
    {
      "reference": "ref 1",
      "definition": {
      }
    },
    {
      "reference": "ref 2",
      "definition": {
      }
    },
    {
      "reference": "ref 3",
      "definition": {
      }
    }
  ],
  "model": [
    {
      "reference": "ref 1",
      "id": 1,
      "state": [
      ]
    },
    {
      "reference": "ref 2",
      "id": 1,
      "state": [
      ]
    },
    {
      "reference": "ref 3",
      "id": 1,
      "state": [
      ]
    }
  ]
}

    Different categories (different models) associated with different Jira projects

    Two categories associated with two different case types (ServiceCall, Problem) are registered, generating the following association:

    Category Case Type Model Jira Project
    1 ServiceCall 1 Project 1
    2 ServiceCall 1 Project 2
    1 Problem 2 Project 1
    2 Problem 2 Project 2
    • Associate the assigned reference in each category with the definition for each project in case:
    Category Jira Project case (reference)
    1 Project 1 ref 1
    2 Project 2 ref 2
    • As specified in the previous table, the categories correspond to different models, so in the “model” We add the property Reference.
    • Associate the aggregated references for each category with the model as follows:
    Category Case Type Model Jira Project model (reference)
    1 ServiceCall 1 Project 1 ref 1
    1 Problem 2 Project 1 ref 1
    2 ServiceCall 1 Project 2 ref 2
    2 Problem 2 Project 2 ref 2 
    {
  "project": [
    {
      "id": 1,
      "service": 2,
      "category": [
        {
          "reference": "ref 1",
          "id": 1,
          "value": "proyecto 1"
        },
        {
          "reference": "ref 2",
          "id": 2,
          "value": "proyecto 2"
        }
      ]
    }
  ],
  "itemType": [
    {
      "reference": "ref 1",
      "type": "ServiceCall",
      "workItemType": "Feature"
    },
    {
      "reference": "ref 1",
      "type": "Problem",
      "workItemType": "Bug"
    },
    {
      "reference": "ref 2",
      "type": "ServiceCall",
      "workItemType": "Feature"
    },
    {
      "reference": "ref 2",
      "type": "Problem",
      "workItemType": "Bug"
    }
  ],
  "case": [
    {
      "reference": "ref 1",
      "definition": {
      }
    },
    {
      "reference": "ref 2",
      "definition": {
      }
    }
  ],
  "model": [
    {
      "reference": "ref 1",
      "id": 1,
      "state": [
      ]
    },
    {
      "reference": "ref 1",
      "id": 2,
      "state": [
      ]
    },
    {
      "reference": "ref 2",
      "id": 1,
      "state": [
      ]
    },
    {
      "reference": "ref 2",
      "id": 2,
      "state": [
      ]
    }
  ]
}