Jira integrations: Storing reference ID / URL of counterpart
Last updated
Last updated
When integrating collaboration tools, users can capture the counterpart IDs/URLs in both trigger and destination tasks. Across different workspaces, the same synchronized task may have different IDs (e.g., JIRA-987 on Jira, Task 53 on Monday). Storing counterpart reference ID/URL facilitates effective cross-platform communication for teams.
This process can be performed with most of the software we support, in case you struggle to map a custom field for the software of you choice please let us know via chat or create a ticket at our Support Portal.
(Verify extra information about the usefulness and downside of this method at the bottom of this page).
Step 1: Make sure to create the custom fields in both workspaces.
For Jira, you can click on the task itself, then scroll down the right tab and click “Configure”
For the ID, we are going to create a text custom field, and for the URL we are going to use a URL custom field (a text custom field can also be used for the URL, but depending on the workspace it will just generate a text and not a link persé).
Simply drag and drop the Short Text and URL fields, and name them per your need:
After creating your custom fields, go back to your Jira workspace, search, and add the new custom fields:
In this example, we are using Monday. Here the process is faster, simply click the “add” button on your workspace columns, then add “text”.
Use the search bar to locate the link custom field, or navigate the available custom fields through the “more columns” button at the bottom of the tab:
Name your custom fields as you desire, so they can reflect the data that you need to fetch from the counterpart:
(The process may vary from software to software, please verify the available instructions on how to create custom fields in your software of choice)
For this integration, Jira is on the left-hand side and Monday is on the right-hand side.
Through the drop-down menu of the available map fields, you need to map two fields for each side:
Make sure to define the direction of the sync, where the arrow points to the custom field.
Warnings were removed after the direction of sync was defined.
Monday ID ↔︎ Id (This map will allow the ‘Monday ID’ custom field in Jira to store the ID of its Monday task counterpart);
Monday URL ↔︎ Url (This map will allow the ‘Monday URL' custom field in Jira to store the Url of its Monday task counterpart);
Id ↔︎ Jira ID (This map will allow the “Jira ID” custom field in Monday to store the ID of its Jira task counterpart);
Url ↔︎ Jira URL (This map will allow the “Jira URL” custom field in Monday to store the Url of its Jira task counterpart);
After concluding the integration, you can run a migration to transfer all data from one side to the other.
At this time, we can verify if the mapping worked and if we can see the mapped fields are filled with the required data:
Above we can see that Jira successfully fetched the ID and URL of these task's counterparts from Monday.
Above we can see that Monday also successfully fetched the IDs and URLs of the task's respective counterparts on Jira.
This setup is especially useful for large filtering and management of a tasks/issues/tickets database.
Whichever teams working together in both workspaces can communicate effectively, refer to one another’s issues with accuracy, and deal with them efficiently.
Addendum: Most software supported by us will allow this type of field mapping.
In the case of needing a development effort to allow this type of field mapping for one of the supported software you chose, please refer to our support portal here.
