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. Interactions

Jira Service Management Requests

Log JSM Tickets as Interactions in Atlas CRM

Last updated 5 months ago

Was this helpful?

Automatically logging service requests from your customers into Atlas CRM ensures that all interactions are tracked in one place, providing a complete view of customer activity. By enabling the Interactions Automations Blueprint for your Jira Service Management (JSM) projects, you can capture these conversations without any manual effort.

You can use this action in combination with the Issue created and Issue comment added triggers to automatically store JSM requests as interactions in Atlas CRM. Additionally, the reporter of the issue will be created as a contact in Atlas CRM if they don’t already exist, ensuring your customer database is always up to date.

Here’s how to set it up:

  • As an admin, navigate to Settings in Atlas CRM (top-right corner) and select Automations.

  • Choose the JSM project where you’d like requests to be logged as interactions.

  • In the blueprint section, select Log issues as interactions and click Use blueprint.

  • Publish the automations, and you’re all set!

From that point forward, any new requests or replies in the selected JSM project will be automatically stored as interactions in Atlas CRM, giving your team an up-to-date view of all customer communications.

Log JSM Tickets as Interactions