Jira Freshservice integration
Last updated
Was this helpful?
Last updated
Was this helpful?
Integrating Jira with Freshservice via the Getint platform transforms how organizations handle project management and customer service in today's interconnected business environment. This essential link creates a streamlined interface that aligns project tracking with IT service management, significantly enhancing operational efficiency and team communication. Our guide offers a clear, straightforward setup process, allowing companies of all sizes to boost collaboration and elevate their service delivery capabilities. Harness the power of the Jira-Freshservice integration with Getint, and move towards a more efficient and effective framework for managing projects and support services.
Navigate to Jira, go to "Apps," and select "Jira - Freshdesk integration"
Choose "Continuous Sync" or "Migration" based on your integration needs.
Visit your Atlassian Account Settings and go to the Security section.
Generate an API token in the API Token section. This token will authenticate your Jira Cloud.
Ensure you're logged in as a user with the correct permissions
Click "Select App" and choose Jira.
Select "Create New" to connect with your Jira instance.
Name your connection, and add the URL of your Jira instance (without "/" at the end).
Provide the login credentials.
With a successful connection, a dropdown menu will appear.
Select the Jira project you want to integrate.
Log in to your Freshservice account, click on your profile picture in the top right corner, and select “profile settings”
On the new page, on the right, click on 'Your API Key' and select the check button to access the API key:
Complete the captcha verification when prompted, and copy the API Key.
Open the Getint app and select "Freshservice" as the connection app.
Enter your Freshservice instance URL and click "Next".
Name the connection and provide your login credentials, using the token captured as the password.
Choose an existing connection or create a new one and select “Connect”
Quick Build:
Consider using the "Quick Build" beta feature for automated type and field mapping. Quick Build automatically performs the mappings based on the most common configurations used by our customers, making it an ideal initial setup for a Minimum Viable Product (MVP). This feature simplifies the setup process by pre-configuring types, fields, and values, allowing you to quickly get started with a functional integration. Once the initial setup is complete, you can review and adjust the mappings to better suit your specific needs and requirements.
Manual Setup:
Select to synchronize Jira issue types such as Task, Bug, Epic, and Story with their Freshservice counterparts.
Define which fields should be integrated or synchronized during this process.
Proper field mapping ensures data integrity across both platforms. Below are essential fields that require mapping:
For the Freshservice connection to work, it is necessary to map some key fields:
Reporter/Requester Mapping:
Link the "Reporter" field in Jira to the "Requester" field in Freshservice.
Ensure that requesters on both platforms are mapped to allow Getint to match them appropriately.
In case a fixed value, like an email, is supposed to be defined for this field, the configuration can be done like this:
Status Field:
Freshservice mandates status mapping for the integration to function. A default value needs to be set for the ticket creation only, pointing towards the Freshservice side, avoiding this option being picked up again when the issues are updated:
Priority Field:
Mapping the priority field is necessary for the integration's operation within Freshservice.
After all fields and types have been configured, give your integration a distinctive name and save the settings.
Consider using the "Quick Build" beta feature for automated type and field mapping, which can streamline the setup process.
It is possible to filter the synchronization to have them customized for your needs and requirements.
UI Filtering Option:
Click on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
Select if the filtering applies to All, New, and Synced items.
Note that if the option “New items” is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option “Synced items” is selected, only the already synced items will be updated based on that filter.
Choose the options and add the value for the filter. It is possible to filter more than one option for each field.
Select Apply once you have created the filters and Save the integration.
JQL Filtering:
Select the app that will receive the filter.
Under the field Custom JQL, it is possible to provide a JQL, which will be the filter for your sync and appended to the one generated when searching for issues in Jira (e.g., status in ('In Progress')).
Save the integration.
Go to Workflows.
Click the 3 dots on the right side and select "duplicate."
A side panel will appear. Select a new name for the integration (by default, the integration will be called “copy of” if the same projects are established).
On the dropdown menu, select the projects you would like to integrate.
For each side, select Connect. Then Duplicate.
Save the new integration.
Quick build is currently in the beta stage, if you have feedback or questions about it, please get in touch with our support at
Quick build is currently in the beta stage, if you have feedback or questions about it, please get in touch with our support at
Leverage the Jira-Freshservice integration by Getint to optimize your customer service processes. For further assistance or feedback, contact
