The integration allows:

1. Relate the ASMS project, service, and category to the Jira project.
2. Case types in ASMS can be related to Issue types, using the “itemType”in the configuration file.
3. Relate the field “subject” with any field of type “Text”.
4. Relate the field “description” with any field of type “Text, Paragraph”.
5. Relate the fields “responsible”, “client” and “applicant” with fields such as “People”, “Text” or “Drop-down menu”
6. Relate the values of the platforms according to the association of the properties in the configuration file (data relationship type: Mapper).
7. Add defaults for properties responsible, responsibleGroup, client, Company, applicant, typeRegister, Ci.
8. The type fields “Comments” in Jira they can only be related to Notes in ASMS cases.
9. The following are presented: Integration scenarios
10. Relate multiple categories to a single Jira project (Only with dataSource: “Aranda”).
11. Creating Jira Cases to ASMS (Only with dataSource: “Both”, “External”),
12. Allows you to associate a model with different categories.
13. Allows you to add constant values to an ASMS or Jira property (data relationship type: Value).
14. Allows you to relate additional ASMS fields to fields in Jira.

Integration NO Allows:

1. Relate the project, service, and category to custom fields.
2. Relating the state to another customizable property is not allowed.
3. No duplication is allowed in ASMS Notes or Issue History.

Restrictions (Important)

• Duplicate files (same name) should not be attached to the case in Jira, this action can generate duplicate attachments in the case of ASMS. This is because ASMS differentiates files by name and does not accept duplicates. Therefore, it adds a consecutive to the name of the duplicate file. This can lead to a file duplication loop.

Relationship between basic fields of the case with the fields of the Issue

Relationship Between Additional Case Fields to Issue Fields