Hooq for ServiceNow.
Record sync with nothing in the middle.

In the preview today

Works today

• Connect ServiceNow with Jira Cloud, or with another ServiceNow instanceTwo administrators connect the two instances.
• New records follow to the other sideBetween two ServiceNow instances, both ways. With Jira, a new ServiceNow record creates a Jira work item, and a new Jira work item creates the ServiceNow record.
• Edits and state changes followEdits to the synced fields of a record follow both ways. A state change is applied by the receiving side, so its own rules apply: for example a Problem needs an assignee and a Change request needs an assignment group before it can leave New. A Change request state change made on the second ServiceNow instance is not yet proven.
• Comments and work notes followBetween two ServiceNow instances, both ways. With Jira, comments follow both ways and work notes arrive in Jira. With Jira Service Management, work notes become internal notes.
• Attachments followBetween two ServiceNow instances, files arrive unchanged and a file sent twice is stored once. Between ServiceNow and Jira, attachments follow too.
• Only the records you chooseLimit a sync to the records that match a condition.
• Set up from screens in ServiceNowCreate a Hooq step by step, save a draft, publish, start and stop.
• Tables in IT Service Management, between two ServiceNow instancesIncident, Problem, Change request, Catalog task and Requested item, both ways.
• With Jira Service ManagementIncident, Change request and Requested item pair with Jira Service Management Incident, Change and Service request work items: edits, public comments, internal notes and status follow both ways. When a request type is set they become customer requests. A Problem pairs with a Jira Problem work item: new records, edits and comments follow, and a status follows only to a status the Jira workflow allows.
• With Jira projectsServiceNow incident, story, epic, scrum task and feature records pair with Jira work items. A Jira Epic, Story, Task or Sub-task with its parent link pairs with an epic, story or scrum task.
• Tables in Agile Development, between two ServiceNow instancesEpic, Story, Scrum task and Feature, both ways. A story keeps its epic and a scrum task keeps its story.
• Tables in Strategic Portfolio Management, between two ServiceNow instancesProject and Project task, both ways: new records, edits, comments and work notes, and the project of a task.