Creating a configuration file
The integration between the platform Aranda Service Management Suite (ASMS) and Jira Cloud, is done by setting up a file in JSON format. It is based on the following conceptual model:
A continuación se presenta la definición del modelo conceptual:
| Properties | Description | |
|---|---|---|
| project: | Relate the ASMS project, category, and service to the project in Jira Cloud | See more |
| Case: | Allows you to relate the fields of the Aranda Case to the fields of the Issue in Jira Cloud | See more |
| itemType: | Relationship of ASMS case types to the “Issue Type” in Jira Cloud | See more |
| model: | Represents the relationship of the status and additional fields in ASMS cases to the status and fields of the “Issue Type” in Jira Cloud | See more |
| typeRegister: | Relate the record type of ASMS cases to the record type in Jira Cloud | See more |
| Responsible: | Match the ASMS case manager with the person in Jira Cloud | See more |
| responsibleGroup: | Match the group responsible for ASMS cases to the group responsible in Jira Cloud | See more |
| Applicant: | Match the requester of ASMS cases to the requester in Jira Cloud | See more |
| Company: | Relates ASMS Cases Company to Company in Jira Cloud | See more |
| Client: | Match the customer of ASMS cases with the customer in Jira Cloud | See more |
| Ci: | Relate the CI of ASMS cases to the CI in Jira Cloud | See more |
| IdByProject: | Relate the idbyproject of ASMS cases to a short text field in Jira Cloud | See more |
| Impact: | Represents the relationship of criticality ASMS cases to Jira Cloud cases | See more |
| Urgency: | Represents the relationship of criticality ASMS cases to Jira Cloud cases | See more |
Information to take into account:
- Restrictions
- Instructions for getting the ASMS id’s used in the configuration file, using the ASMS API with the postman tool Instructions here
Below you can download the json structure that will be used throughout the documentation.