Remedy change requests to Jira tasks

Use Case

#	Remedy	Jira
Connected Systems	Remedy	Jira
Authentication (supported methods)	Username and Password	Username and Password (server) Username and API Token (cloud)
Permissions	Remedy Form: AR System Metadata ARSchema (READ) Change Request Master and Change Request Viewer Support Staff → Yes Support Group Member → Yes Access Restriction → Unrestricted Access	Add Comments Assign issues Browse Projects Create Attachments Create Issues Edit Issues Resolve Issues Transition issues
Environment	N/A	Correlation Field API Token (cloud)

Log in to your ZigiOps instance.
Go to ZigiOps → Configurator and load the integration template.
Select the desired Integrated Systems and Integrated Systems and click the Save button to continue.
Update the correlation configuration by replacing the default Jira custom correlation field (~~customfield_10100~~) with the custom correlation field you've created earlier and click the Save button to continue
Enable the integration from the Slider button located in the middle section of the screen.

When there is a new change request in Remedy, ZigiOps will automatically collect it, based on a predefined time interval, and transfer it to Jira as a new task. All necessary fields will be transformed and also moved to Jira (based on the defined mapping in ZigiOps).
If there is an update on the Remedy change request, ZigiOps will pick it up and populate the corresponding Jira task with the necessary fields (comments, attachments, custom fields, and more).
When the Jira task is closed or updated, ZigiOps will update the corresponding change request in Remedy with the applicable information or close it accordingly.

Visit our website for more information, about our Remedy Jira integration.

No specifics are available for this integration.