Storing Reference IDs/URLs Across Integrations

When integrating tools with Getint, users can capture counterpart IDs/URLs in source and destination tasks. This is particularly valuable when tasks synchronized between platforms have different identifiers. Storing these references improves cross-platform collaboration, allowing teams to communicate effectively and manage tasks more efficiently.

This method can be applied across any supported integration. If you encounter difficulties mapping custom fields in your preferred software, don't hesitate to contact us at our Support Portal.

Creating Custom Fields

Step 1: Create Custom Fields

Ensure you create the required custom fields in both workspaces:

1. Open a task and scroll down the right-hand panel.

2. Click Configure to create a new custom field.

1. Add:

• Text Field for IDs.

• URL Field for links (or use a Text Field if URL fields aren’t supported).

1. Add the fields to your layout, name them appropriately, and save the changes.

The process for creating custom fields varies between software platforms. Check our documentation for guidance

Step 2: Map Custom Fields

In Getint, map the custom fields between the two platforms. Here’s an example for Jira (left) and Jira (right):

1. Use the drop-down menus to map the following fields:

   • ID (On Jira Left) ↔︎ Jira Reference ID

• URL (On Jira Left) ↔︎ Jira Reference URL

• Reference ID (custom field) ↔︎ ID (On Jira Right)

• Reference URL (custom field) ↔︎ URL (On Jira Right)

1. The fields are one-directional as the data from fields like ID and URL are read-only and cannot be modified:

Ensure the fields are mapped correctly to avoid errors or missing data.

Important Warning for ServiceNow Users When integrating ServiceNow (SNOW), if you want the Ticket Number to be referenced, you should use Number instead of ID.

• Number → Brings the actual ticket reference (e.g., INC0001234).

• ID → Brings the system-generated unique identifier (a much larger numeric value). Selecting the wrong field may result in incorrect references being stored.

Step 3: Test the Integration

After setting up the integration:

1. Run a migration or sync to transfer data between platforms.

1. Verify that mapped fields are populated with the correct data:

   • Jira Right fields should contain the IDs and URLs of the corresponding Jira Left tasks.

   • Jira Left fields should contain the IDs and URLs of the corresponding Jira Right tasks.

Note that already synchronized issues will not be updated with URLs and Reference IDs unless migration is performed.

Why Use Reference IDs/URLs?

Storing reference IDs/URLs is especially helpful for:

• Filtering and Database Management: Simplifies handling large volumes of tasks/issues/tickets.

• Effective Collaboration: Teams across platforms can reference tasks accurately and resolve issues efficiently.

Important!

This setup applies to most integrations supported by Getint. For tools needing custom field mapping that require further development, please reach out through the Support Portal. Our team is here to assist with your integration needs.

Let us know if further adjustments are needed!

Start your integration journey. Schedule a free consultation with our Getint Integration Expert today!