Troubleshooting
Jira Cloud
If you are using Jira Cloud, please:
go to Custom Fields page
find your custom field and click option Associate to Screens
on Screens page, please make sure that checkbox is ticked for the project you are integrating
click Update button
refresh page in getint.io app and check again if field appears or not
​
If you do not see still field on a list, or you are using other app than Jira Cloud, please submit a support ticket https://getintio.atlassian.net/servicedesk/customer/portals. We will try to help you.
Migration Run can be stopped on Integration Thread view:
navigate to Analysis -> Integration Threads page
when integration is running, STOP RUN button should appear
click the button to stop run
Run will stop as soon as synchronization of the item currently being processed has finished
Sometimes there is a need to combine two or more field into a one field in a synced item. There are difference use cases and reasons for doing these, like lack of creating custom fields in the destination app.
In the example, we will show you how to combine Jira Issue Key and Jira Issue Title(Summary) into a one field, Azure Title. For that you need to:
add a mapping for a Predefined Value on the Jira side (in our case Left side) with the Title field on Azure side (right side). Predefined value should be: ${left.id} - ${left.title}
because it can be only one way sync, click on a ARROW icon to point it to the right side
because we are using ${left.title}, which will be translated to value of Title field, getint.io must be somehow aware of what is definition of Title field. For that we are adding another mapping of Jira Title field with Predefined value on Azure side equal to n/a
save integration
So from now on, when Jira issue is created,
getint.io will combine value for title of the new Azure item as ID + TITLE of Jira issue.
You can achieve this by filling a Predefined Value field when adding a fields mapping. E.g. we would like to insert fixed value into a Title field. This is how the mapping should look like, before we create it.
Now just click Add button to create a field mapping.
Filtering of comments which should be picked up for sync can be done on Type Mapping level. This feature is supported only by ServiceNow and Jira Service Desk apps where comments can be private or public. To filter comments you need to:
click the Type Mapping for which you want to filter comments
click Comments & Attachments tab
fill logical condition. If the source of comments (e.g. Jira) is on left hand side of your integration, provide logical condition for left hand side
for Jira Service Desk:
${comment.jsdPublic} = true- this will use that logical and compare each commentjsdPublicproperty to true. So the private comments, which hasjsdPublicbeing false will not pass the condition and will be skippedfor ServiceNow:
${comment.isPublic} = true- same as for Jira, it will sync only public comments. Work notes will be skipped
save integration
If you are not syncing Jira issue status with Asana section, but Asana custom field, then it requires providing some workaround. Lets say you have created a "Status" field in asana being a dropdown with options corresponding Jira statuses.
After configuring status sync on Status tab like below:
You need to make getint.io aware of the definition of Asana custom field (Status). To do that you need:
go to Field tab
add field mapping for the Status field which will be never used, but will provide getint.io awareness that status field exists
provide n/a into a predefined value on the other side
select Status field from dropdown on Asana side
click Add button
deselect ON CREATE and ON UPDATE actions by clicking on highlighted buttons. So Status field won't be changed by getint.io during field updates. It will still be handled during statuses sync so no worries.
save integration
