Atlas CRM Cloud
  • Atlas CRM Cloud
  • Release notes 2025
  • Release notes 2024
  • Release notes 2023
  • Release notes 2022
    • November 21st
    • September 8th
    • June 14th
    • June 1st
    • May 19th
    • May 11th
    • March 31st
    • March 15th
    • March 9th
    • March 2nd
    • February 21st
    • February 16th
    • February 4th
    • February 2nd
    • January 22nd - Atlas CRM 2.0
    • January 13th
    • January 10th
  • Getting started
    • Checklist
    • Core concepts
    • Installation
    • Language settings
    • Pricing
  • User functionalities
    • Companies
    • Contacts
    • Sales
    • Jira issues
    • Interactions
      • Manual Interactions
      • Gmail Integration
        • Installation
        • Feature overview
        • Admin settings
      • Outlook Integration
        • Installation
        • Feature overview
        • Admin settings
      • Jira Service Management Requests
    • Custom JQL
      • Practical examples
      • Queues in Jira Service Management
      • Gadgets on dashboards
      • Custom JQL automations
    • Confluence pages
    • Export
    • User preferences
  • Gmail integration
  • Admin configuration
    • Templates
    • Import
    • Sales configuration
    • Atlas CRM data on Jira issues
    • Access and User roles
      • Granting access to Atlas CRM
      • Customising User roles
    • Automations
      • Triggers
        • Issue created
        • Issue comment added
        • Issue updated
        • Contact linked to issue
        • Company linked to issue
        • Sale linked to issue
      • Actions
        • Link company based on custom field
        • Link contact based on custom field
        • Link contact based on reporter's email
        • Link company based on reporter's email
        • Copy template fields to custom fields
        • Link a linked company
        • Link a linked contact
        • Log issue as interaction
      • Configure an automation
        • Select trigger and actions
        • Publishing your automation
        • Disabling an automation
    • User synchronization
    • JSM Connect
    • API
      • Authentication
      • Endpoints
  • Privacy / Security
    • Security policy
  • Relevant links
  • Marketplace
  • Support
  • Roadmap
  • Server / Data Center documentation
Powered by GitBook
On this page

Was this helpful?

  1. User functionalities
  2. Custom JQL

Custom JQL automations

Expanding Custom JQL Use Cases with Automations

Last updated 7 months ago

Was this helpful?

Atlas CRM’s Custom JQL not only lets you query your data but also integrates seamlessly with Jira automations, making it possible to trigger automations based on customer or sales information.

Example:

Automate notifications for VIP customer issues across all projects

With Atlas CRM’s Custom JQL, you can create rules to stay on top of issues linked to high-priority customers, like those with "VIP" status. This example shows how to set up a scheduled rule to send email notifications when issues are linked to VIP customers, ensuring timely attention.

How to set up a system-wide automation for VIP customers:

  1. Go to Jira Settings > System > Automations

  2. Create a new rule Select "Create Rule" and choose the "Scheduled" trigger.

  3. Configure the schedule Set the rule to run at your preferred interval (e.g., every 10 minutes). The rule will check for updates across all Jira projects.

  4. Add a JQL condition In the "Conditions" section, input the following Custom JQL query to identify issues linked to customers with VIP status:

    atlasCompany in atlasCompanies("Customer Tier", "=", "VIP")

    This will ensure the rule only targets issues associated with VIP customers.

  5. Add an action Choose the "Send Email" action and configure the email to notify you (or any designated team members) when a new issue related to a VIP customer is identified.

    Example email message:

    {{issue.key}} has been linked to VIP Customers

  6. Save and enable the rule Once you've configured the rule, save and enable it. This ensures that you'll receive an email every time the rule finds an issue linked to a VIP customer.

This rule is just an example. It works at the system level, meaning it will apply to all Jira projects. The rule will also trigger an email notification when a customer’s tier is upgraded to VIP and issues are already linked to that customer.

Example of a scheduled rule to send email notifications when issues are linked to VIP customers
Example of an email that is sent based on this rule