How to Create Automatic Jira Tickets from Slack Messages

In today's fast-paced work environment, communication often happens in real-time on platforms like Slack. While Slack is excellent for quick discussions and instant updates, important requests, tasks, and issues can easily get lost or overlooked amidst the stream of messages. Manually transferring these items into a project management tool like Jira is time-consuming, repetitive, and prone to human error.

Imagine a world where every critical request mentioned in Slack automatically becomes a trackable task in Jira. This tutorial will show you how to set up an automation that bridges the gap between your real-time conversations and your structured task management, ensuring nothing falls through the cracks. This setup will save your team valuable time, improve accountability, and keep your projects on track.

Why This Matters for Your Business

Automating the creation of Jira tickets from Slack messages offers significant benefits for any business, freelancer, or operations manager:

• No Missed Tasks: Critical requests or bugs reported in Slack are instantly captured in Jira, reducing the risk of them being forgotten.
• Time Savings: Eliminate the manual effort of copying and pasting information between Slack and Jira, freeing up your team for more strategic work.
• Improved Accountability: Every ticket created has an assignee, a due date, and a clear description, making it easier to track progress and identify responsible parties.
• Consistent Workflow: Standardize how issues and requests are logged, ensuring all necessary information is captured from the start.
• Better Reporting: With all tasks in Jira, you gain a clearer overview of your team's workload, bottlenecks, and project progress.

Step-by-Step Guide: Automating Jira Tickets from Slack

We'll use an integration platform to connect Slack and Jira. For this tutorial, we will use Make.com, a visual automation builder that requires no coding.

1. Step 1: Prepare Your Accounts

   Before you begin, ensure you have:

   • An active Slack workspace where you have permission to add apps.
   • An active Jira account with permissions to create issues in a specific project.
   • A Make.com account (you can start with their free tier).

2. Step 2: Create a New Scenario in Make.com

   Log in to your Make.com account. On the dashboard, click the "Create a new scenario" button. This is where you'll build your automation.

3. Step 3: Set Up the Slack Trigger Module

   In your new scenario, click the large circle with a plus sign. Search for "Slack" and select the Slack app. Choose the "Watch new reaction" module. This module will trigger your automation every time a specific emoji reaction is added to a Slack message.

   • Connect Slack: Click "Add" to connect your Slack workspace. Follow the prompts to authorize Make.com to access your Slack account.
   • Choose Reaction: Select the emoji you want to use to trigger ticket creation. For example, you could use :jira:, :ticket:, or a simple :pushpin:. This makes it easy for anyone in your team to flag a message for Jira.
   • Select Type of Event: Choose "Message reaction added."

4. Step 4: Add a Router (Optional, but Recommended)

   A router lets you create different paths for your automation based on conditions. For instance, if you want different Jira issue types for different reactions, or only want to proceed if the reaction is on a specific channel. For now, we will use it simply to ensure we are only processing the first added reaction. Click on the half-circle with a plus sign, search for "Flow Control", and select "Router". Connect it to your Slack module.

5. Step 5: Set Up the Jira Action Module

   Now, connect a Jira module to your Router. Click the plus sign next to the Router, search for "Jira," and select the "Create an Issue" module.

   • Connect Jira: Click "Add" to connect your Jira account. You'll need your Jira site URL and API token or username/password.
   • Project: Select the Jira project where you want the tickets to be created (e.g., "Software Development," "Operations," "Freelance Projects").
   • Issue Type: Choose the type of issue you want to create (e.g., "Task," "Bug," "Story," "Service Request").
   • Summary: This will be the title of your Jira ticket. You can map this directly from the Slack message text. In Make.com, you can drag and drop variables from the Slack module's output, such as Text or Message Content.
   • Description: Provide more detail. You can combine information, such as the full Slack message content, the user who posted it, and a direct link back to the Slack message. Use variables like Text (from Slack), User Name (from Slack user details), and Permalink (from Slack message details).
   • Reporter: Map this to the Slack user who posted the message, if their email matches a Jira user.
   • Other Fields: You can map other fields like "Priority," "Assignee," or custom fields if available in your Jira setup.

6. Step 6: Optional: Post Confirmation Back to Slack

   It's good practice to let the original Slack user know that a Jira ticket has been created. Add another Slack module after the Jira module, choosing "Create a message."

   • Connection: Use your existing Slack connection.
   • Channel ID: Map this to the Channel ID from the initial Slack trigger module to post the confirmation in the same channel.
   • Text: Craft a message like "Jira ticket created! [Jira Ticket Key]" and use variables from the Jira module's output (e.g., Key and URL) to provide the direct link.

7. Step 7: Test and Activate Your Scenario

   Click the "Run once" button at the bottom left. Then, go to your Slack workspace and add your chosen emoji reaction to a message. Watch the magic happen in Make.com and then check your Jira project. If everything works as expected, toggle the scenario "ON" to activate it permanently.

Pro Tips for Advanced Automation

• Specific Channels: If you only want reactions from certain Slack channels to trigger Jira tickets, you can add a "Filter" between the Slack and Jira modules in Make.com, checking for the Channel ID.
• Template Jira Issues: For recurring requests, create a Jira issue template and have your automation populate specific fields to maintain consistency.
• Conditional Logic: Use Make.com's "Filter" tool to create different Jira issues based on keywords in the Slack message (e.g., if a message contains "bug," create a "Bug" issue type; if it contains "feature request," create a "Story" issue type).
• Attachments: If a Slack message has attachments, you can configure your automation to download them from Slack and upload them to the newly created Jira ticket. This is a more advanced step but highly valuable.

Frequently Asked Questions (FAQ)

1. Can I map the Slack message content to specific custom fields in Jira?

Yes, absolutely. When configuring the "Create an Issue" module in Jira on Make.com, you will see an option to "Add custom fields." You can then select your custom fields and map specific pieces of information from the Slack message (or other modules) to populate them.

2. Does this automation work for private Slack channels or direct messages?

Yes, it can. When you connect your Slack account to Make.com, you grant it certain permissions. Ensure that Make.com has access to the private channels or direct messages you wish to monitor. The Slack "Watch new reaction" module will then function as intended, provided the bot is a member of those channels.

3. How much does this automation cost?

Make.com offers a free tier that includes 1,000 operations per month, which is often sufficient for small teams or initial testing. As your usage grows, you can upgrade to paid plans that offer more operations and advanced features. The cost will depend on the volume of tickets you automate and the complexity of your scenarios.

Written by Vangari Sai Sampath, Automation Specialist · Integration Directory · Hyderabad, India