You can use Sales CRM’s custom fields to create custom JQLs.
Custom JQL enables you to filter and query Jira issues using customer, contact, or sales data from Sales CRM. This feature streamlines work organization and tracking for specific business activities without requiring additional configuration.
The Custom fields that work with the JQL are the following:
Deal
Account
Contact
With a JQL query, you’re able to find support tickets, client projects, or other relevant work items. This integration can help you find items with the right context more easily by plugging the Sales CRM custom fields into Jira searches and filters.
Custom JQL requires no additional configuration in Sales CRM. Once installed, it integrates seamlessly with Jira, allowing you to query tickets based on customer or sales data instantly. Simply use the provided syntax to create queries in Jira and begin leveraging this functionality immediately. |
If you’re not familiar with JQL - you can find out more about them through Atlassian’s documentation here: https://support.atlassian.com/jira-service-management-cloud/docs/use-advanced-search-with-jira-query-language-jql/ |
A popular way of using a JQL in Jira is to use it to search for specific issues that fit a certain criteria, but you could also save a JQL as a filter to find a certain set of issues quickly in the future.
Queues in Jira Service Management (JSM): Easily find tickets based on the Prioritize tickets based on customer tiers or account managers.
Dashboards: Visualize work related to specific customers or sales stages.
Automations: Expand Custom JQL Use Cases with Automations
These custom fields use the exact same operators that you would typically use for JQL. More specifically:
Supported Operators by Custom Field:
Deal (or "issue.property[type_crm_deals].name") : =, !=, IS, IS NOT, IN, NOT IN
Contact (or "issue.property[type_crm_accounts].name") : =, !=, IS, IS NOT, IN, NOT IN
Account (or "issue.property[type_crm_contacts].name") =, !=, IS, IS NOT, IN, NOT IN
When you use : =, !=, IS, IS NOT, the Search Query will expect “EMPTY”.
When you use IN or NOT IN, the Search Query will expect the following options :
EMPTY
typeAccounts("", "", "") →
typeContacts("", "", "") →
typeDeals("", "", "") →
You can find more information on the Atlassian documentation pages: https://support.atlassian.com/jira-software-cloud/docs/jql-fields/