Jira Servicenow integration

[Ben_Wade]

Hello everyone,

I work in the BI department and manage all the issues in Jira. All requests to our department come from So when someone creates a ticket using this form a task will be created. "Subject" and "description" in ServiceNow should be mapped with "description" in Jira, attachment with attachment, requester with a custom field requester that I will create in Jira. That's it.

Guys, if it is achievable, help me please with this task.

#jira # servicenow 

[Ben_Wade]

Do you know what is difference between these two plugins:
Jira Spoke

Jira sevice management Spoke

Which one should I use?

[Vishal36]

Hi @Ben_Wade 

There are several ways to integrate Jira with ServiceNow, depending on the specific use cases and requirements of the organization.

If you are looking for a simple solution that does not require technical expertise, you can choose OpsHub’s Community Edition . A ServiceNow partner, OpsHub offers a federated integration platform to help ease your integration journey. It supports all System (Tasks, Epics, Bugs, Stories) and Custom Issue Types, Sub-Task Types on Jira, and all System (Incidents, Problems, Requests, Changes, etc.) and Custom Tables on ServiceNow.

The flexibility of OpsHub integration allows you to synchronize any data in ServiceNow with any issue type in Jira and vice versa. Additionally, OpsHub offers support for a diverse array of tools. For your reference, you may explore some of the top five most requested integrations with Jira here.

Also, have look at the Jira – ServiceNow documentation and a video to know how OpsHub Integration Manager facilitates a bidirectional integration between Jira and ServiceNow.

OpsHub also takes care of the following use cases:

• Format retention: ServiceNow uses HTML text formatting, while Jira uses Wiki markup text formatting. OpsHub retains the format when integrating data between Jira and ServiceNow.
• Assignment group – project: Jira users use Projects, whereas ServiceNow users often use 'Assignment Group' or some other field for organizing their data. Suppose an issue is associated with a specific group in ServiceNow. If the group is changed, our solution can automatically move or create the issue in another project in Jira as per your defined mapping. This way, your data stays organized and reflects the latest changes.
• Field-level conflict management: In the case of bidirectional integration, data may be updated simultaneously in Jira and ServiceNow, causing conflicts. OpsHub supports Field-level conflict management to maintain consistent data across Jira and ServiceNow.
• Orphaned or Deleted issues/tickets Identification: Our integration solution goes beyond simple create/update operations. It also intelligently handles orphaned or deleted entities, ensuring that all records remain in sync between the two systems. This way, you can maintain data integrity and avoid any discrepancies.
• Criteria-Based Data Integration: OpsHub allows you to define specific criteria for data integration, enabling you to synchronize only the subset of data that meets your specified conditions. This targeted integration helps optimize performance and data relevance.

You can reach out to OpsHub Integration Experts to learn in detail on how to accomplish Jira-ServiceNow integration. 

Thanks, 

Vishal