Migration or mirror, both without writing back
One-off full import for a migration or a continuous mirror for parallel operation. In both cases JSM stays the leading system; isidaten reads and writes nothing back.
← All integrations
IT service management Reads data
Jira Service Management
Tickets, changes and problems from JSM inside isidaten ITSM, without JSM giving anything up
Anyone running their service desk in Jira Service Management wants to keep it there. The connector still brings the tickets to where incident, risk, change approval and evidence meet: the isidaten ITSM module. Once as a full import with comments, attachments, history and customers, or continuously as a mirror that follows via delta reconciliation and webhook and tracks deletions. JSM stays leading; isidaten writes nothing back. Assets from JSM Assets are adopted as IT systems, Confluence articles as ITSM knowledge articles.
Vendor: Atlassian · www.atlassian.com/software/jira/service-management
What is synchronized automatically
- Tickets with comments, attachments and history
- Problems, changes, parent tickets and CAB approvals
- Customers and organisations
- JSM Assets as IT systems, Confluence as knowledge articles
Your benefits
Deletions come along
The delta reconciliation detects what has vanished in JSM, and a reconcile aligns the stock instead of leaving ghost tickets behind.
Connect Jira Service Management with isidaten
We show you the connector live in your own environment – non-binding and free of charge.