The integration allows:
- Relate the ASMS project, service, and category to the Jira project.
- Case types in ASMS can be related to Issue types, using the “itemType”in the configuration file.
- Relate the field “subject” with any field of type “Text”.
- Relate the field “description” with any field of type “Text, Paragraph”.
- Relate the fields “responsible”, “client” and “applicant” with fields such as “People”, “Text” or “Drop-down menu”
- Relate the values of the platforms according to the association of the properties in the configuration file (data relationship type: Mapper).
- Add defaults for properties responsible, responsibleGroup, client, Company, applicant, typeRegister, Ci.
- The type fields “Comments” in Jira they can only be related to Notes in ASMS cases.
- The following are presented: Integration scenarios
- Relate multiple categories to a single Jira project (Only with dataSource: “Aranda”).
- Creating Jira Cases to ASMS (Only with dataSource: “Both”, “External”),
- Allows you to associate a model with different categories.
- Allows you to add constant values to an ASMS or Jira property (data relationship type: Value).
- Allows you to relate additional ASMS fields to fields in Jira.
Integration NO Allows:
- Relate the project, service, and category to custom fields.
- Relating the state to another customizable property is not allowed.
- No duplication is allowed in ASMS Notes or Issue History.
Relationship between basic fields of the case with the fields of the Issue
| ASMS field name | Name field in Jira | AIC field name |
|---|---|---|
| Subject | [summary], [Custom] Guy: Text |
case.definition.subject |
| Description | [description], [Custom] Guy: Paragraph |
case.definition.description |
| Case | [Custom] Guy: Text | case.definition.idByProject |
| Applicant | [assignee], [Custom] Guy: Text, People, Drop-down menu |
case.definition.applicant |
| Operator, Client | [assignee], [Custom] Guy: Text, People, Drop-down menu |
case.definition.client |
| Company | [Custom] Guy: Text, Drop-down menu | case.definition.company |
| CI | [Custom] Guy: Text, Drop-down menu | case.definition.ci |
| Type Register | [Custom] Guy: Text, Drop-down menu | case.definition.typeRegister |
| Responsible Group | [Custom] Guy: Text, Drop-down menu | case.definition.responsibleGroup |
| Responsible | [assignee], [Custom] Guy: Text, Drop-down menu |
case.definition.responsibleGroup |
| Status | EndPoint {/rest/api/3/issue/{issueIdOrKey}/transitions} | model.state |
| Reason | [Custom] Guy: Text, Drop-down menu | model.state.reason |
| Impact | [Custom] Guy: Text, Drop-down menu, | impact |
| Urgency | [Custom] Guy: Text, Drop-down menu, | urgency |
| Notes | [comment] | NA |
| Solution | [Custom] Guy: Paragraph |
model.state.commentary |
| Priority | NA | NA |
| Provider | NA | NA |
| UC | NA | NA |
| Organizational Area | NA | NA |
| WAVE | NA | NA |
| SLA | NA | NA |
| Contract | NA | NA |
Relationship Between Additional Case Fields to Issue Fields
| Field Type in ASMS | Field type in Jira | AIC field name |
|---|---|---|
| Short Text | Text | model.additionalFields |
| Paragraph | Paragraph | model.additionalFields |
| Date and Time | Date/Time | model.additionalFields |
| Numeric | Number | model.additionalFields |
| Decimal | Number | model.additionalFields |
| Link | Text | model.additionalFields |
| List | Drop-down menu, Text, Number | model.additionalFields |
| Catalog List | Drop-down menu, Text, Number | model.additionalFields |
| True or False | Boolean | model.additionalFields |