OVERALL RATINGS
SUPPORT
- Partner Supported
Key highlights of the appYour ITSM team flags it in BMC Remedy. Your devs fix it in Jira. ZigiOps makes the handoff instant — two-way, zero code
ZigiOps comes with intuitive UI design
A centralized dashboard that unifies integration data in real time, minimizes errors, and enables faster, more informed responses.
Various pre-defined integration templates
Pick and load one of ZigiOps pre-defined integration templates and save time and resources.
Customizable and scalable mapping
Customize any part of the workflow as needed, and effortlessly scale up your projects as you grow.
Supporting media
More details
📆 Book a demo | ✅ Free Trial| 💻 Demos/Tutorials
An incident hits BMC Remedy at 2am. By the time your on-call dev opens Jira, the ticket is already there — fully populated, prioritized, and ready to action. No one filed it. No one copy-pasted it. ZigiOps already did.
ITSM teams stay in Remedy. DevOps teams stay in Jira. Neither needs access to the other's tool, yet both work from the same live data. Comments thread across systems. Attachments travel with the ticket. Status changes close the loop automatically — from first report to final resolution, without a single manual touchpoint.
This isn't a connector. It's the missing layer between your ITSM and engineering workflows — secure, no-code, and built to handle the incidents that can't wait for a morning standup.
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Version information
Version 3.2.2•for Jira Cloud
- Release date
- Aug 2nd 2022
- Summary
- BMC Remedy integration for Jira by ZigiOps (no-code, two-way sync)
- Details
Every minute a Remedy incident sits unactioned in Jira is a minute your customer is waiting. ZigiOps eliminates that minute entirely.
Incidents, Change Requests, and custom records flow from Remedy into Jira the moment they're created — with full context, live status, and every comment and attachment in tow. Your helpdesk never chases a dev for an update. Your devs never log a bug manually. Both teams see the same truth, in their own tool, without ever crossing into the other's.
What travels automatically:
- Remedy Incidents, Change Requests, and custom records
- Jira Issues with comments, attachments, and full lifecycle status
- Real-time updates in both directions until resolution
No chasing. No copying. No customer left waiting on a handoff that never happened.
- Payment model
- Paid via Vendor
- License type
- Commercial