Request type issue on Jira Service Management how to select and work with it
PreviousNotificationsNextIntegrating one project with many: Streamlining synchronization across multiple projects.
Last updated
Was this helpful?
Last updated
Was this helpful?
When integrating with Jira Service Management (JSM) through Getint, users often encounter the additional complexity of request types, which differ from standard issue types in Jira Software. This guide will walk you through the process of mapping request types in JSM to ensure smooth integration and synchronization with other tools like Freshdesk.
In Jira Service Management, request types are specific categories of issues that users can raise, such as "IT Help," "Service Request," or "Incident." These request types are very often mistaken with issue types and are not directly available for mapping in the type mapping section of Getint, which can lead to confusion.
Map "Service Request" in Jira to "Incident" in Freshdesk.
Map the issue types as usual. For example, map "Service Request" in JSM to "Incidents" in Freshdesk.
Ensure all fields are correctly mapped between the two platforms.
In the filter settings, set the request type field to "contains" and the value to "Emailed Request."
Set up the filter:
Field: Request type
Operator: Contains
Value: "Emailed Request"
Once you have set up the filter, you can define how this request type will be handled by the integration. For instance, if you are integrating with Freshdesk and want incidents in Freshdesk to create "Emailed Requests" in Jira Service Management:
Add field mappings for the request type.
Select the app, then Jira, then request type, and map it to a fixed value, such as "Emailed Request."
After completing the request type mapping, the integration will handle data as follows:
Issue Creation: When a new issue is created in the integrated tool (e.g., Freshdesk), the integration will recognize the mapped issue type and request type. It will then create the corresponding issue in Jira Service Management, ensuring that the correct request type (e.g., "Emailed Request") is applied.
Field Synchronization: All mapped fields, including the request type, will be synchronized according to the integration settings. This ensures that any updates to the issue in one platform are reflected in the other, maintaining consistency.
Filtering and Customization: By setting up filters, such as the "Request Type" filter, you can customize which specific types of requests are synchronized. This allows for a more tailored integration that meets the unique needs of your workflow.
For more complex scenarios, such as controlling the request type from other integrated tools, you can use dropdown fields to map request types dynamically.
Create a Dropdown Field:
In the external tool (e.g., Freshdesk), create a dropdown field with options that correspond to Jira request types.
Map Dropdown to Request Type:
In Getint, map the dropdown field to the request type field in Jira. This allows the integration to dynamically set the correct request type based on the dropdown selection.
Consistent Naming: Ensure request types and their corresponding fields have consistent names across platforms.
Test Configurations: Test the mappings and filters in a sandbox environment before deploying them in a live setting.
Documentation: Document the mappings and configurations to ensure all team members understand how request types are managed.
Integrating request types in Jira Service Management with other tools can be complex, but by following this guide, you can ensure accurate and efficient synchronization. For additional support or to provide feedback, don't hesitate to get in touch with our .
