> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/guides/integration-synchronization/jira-servicenow-integration/integrating-multiple-jira-projects-into-a-single-servicenow-instance.md).
# Integrating Multiple Jira Projects into a Single ServiceNow Instance
With our **many‑to‑one** feature, users can integrate multiple Jira projects into a single ServiceNow instance. Because of ServiceNow’s specific architecture, certain configurations need to be handled differently, including **item routing**.
This guide explains how to connect several Jira projects to a single ServiceNow instance and define the rules that determine which Jira project receives each ServiceNow work item, whether that is Project A, B, C, or any other.
{% hint style="warning" %}
**ServiceNow Integrations:**
When configuring many-to-many sync with ServiceNow, **Sync many projects** will only be available on the source app side (i.e., Jira).
Getint connects to the entire **ServiceNow instance** (not individual projects), so configure **Item Routing** in the source app to route tickets from ServiceNow.
{% endhint %}
### Creating a One-to-Many Integration
1. To synchronize multiple projects, begin by creating an integration as you normally would. Next, choose Jira as the connector on the left side.
2. Next, either select an existing connection or create a new one. After the connection is set, you’ll see a checkbox labeled **Sync many projects** above the dropdown list.
3. Select the projects you want to sync, then click **Connect**.
{% hint style="info" %}
An **X** appears next to each project name. Click it to remove a project from the selection if you chose the wrong one.
{% endhint %}
4. Select ServiceNow as the counterpart application, then either create a new connection or select an existing one.
{% hint style="warning" %}
Unlike many-to-many project syncing, Jira-ServiceNow integrations only require selecting many projects from the Jira side. ServiceNow lacks individual projects, so we connect to the **entire instance** (not specific boards).
{% endhint %}
5. Click **Start with Mapping Types** to map the work item types.
6. After mapping issue types, you can start adding fields to them. At the time we’re publishing this article, the **Quick Build** feature is not available for many-to-many projects. You will need to map fields manually.
#### Defining Conditions in Items Routing
The next step is to define conditions, as routing refers to the path a work item takes across connected systems. By setting clear rules, you ensure Getint knows which project each incoming work item belongs to and what type it should have.
Since ServiceNow is treated as a single instance rather than a workspace with multiple projects, you configure routing for items syncing from ServiceNow to Jira, meaning the criteria fields are from the ServiceNow work items.
Please follow the next steps to set up the rules for syncing your items, and then review the subsequent configuration steps to confirm that transitions, field mappings, and workflows are properly aligned.
{% hint style="warning" %}
When populating the operator field values as criteria for the items syncing from ServiceNow, use the Sys ID of the ServiceNow field values instead of the text values. This process will be broken down below.
{% endhint %}
1. Select the project where the item coming from ServiceNow will be routed to, and specify which issue type it should sync as.
2. To collect the Sys ID of the field values, you just have to right-click the value (while on the work items list view) and click **Copy sys\_id**. Paste the copied value, with CTRL/Command + V or right-click > paste, on the operator value afterwards.
\
3\. Choose the field that will trigger the sync. For example, click **+Add New Field** to add conditions across multiple fields. If all conditions are met, the item will sync to the project you are routing it to.
4. Click **Apply** to submit the changes, then save the integration. After that, test the integration to confirm that routing works correctly and items are syncing as expected.
#### Removing or Adding Projects to Existing Integrations
You may need to adjust the projects connected to an integration. This can involve adding new projects to expand its scope or removing existing ones to simplify or restructure it. Follow the steps below to make these changes:
* Click the box for the Jira app. In this example, it is on the left side of the integration.
* Use the dropdown list to browse your projects and add new ones. You can also remove projects from the integration by clicking the **X** icon next to the project name. This works the same way as when you added or removed projects during the initial setup.
* Close the tab and save the integration to submit your changes.
{% hint style="warning" %}
You need to define new conditions to route work items to any new project you’ve added.
{% endhint %}
### Conclusion
As ServiceNow is more complex than most IT management software, there are a few considerations to take into account when connecting it to multiple Jira spaces.\
Tweak your integration until the data is syncing as expected, observe the receiving end of the synchronization to ensure that work items are being created under the configured type, keep in mind that the operator values are based on the Sys ID of the ServiceNow field values, and let the integration take care of the synchronization once everything is up and running.
Need more help? Visit our [Help Center](https://getint.io/help-center) or reach out to support by clicking the chat bubble for direct assistance.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.getint.io/guides/integration-synchronization/jira-servicenow-integration/integrating-multiple-jira-projects-into-a-single-servicenow-instance.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.