Jira Slack Integration | Actioner App Directory





Manage and track Jira issues in Slack with Actioner. Start using the app in Slack immediately after you install it. Actioner provides a seamless Jira Software Slack integration and allows you improve your project management in terms of meeting deadlines, handling backlogs, and managing priorities. 🔎 Promote transparency among the team. Let everyone see updates and understand what is happening with different tasks. 🧑‍💻 Discuss issues directly from Slack, encourage collaboration and quick problem-solving. ## Features - **Jira notifications on Slack:** Get notified of new issues through smart notifications and track their updates in your preferred channel. - **Take Jira actions on Slack:** Report issues with an 🎫 emoji. View, assign, change status, log work, and comment on issues within Slack. - **Dedicated channels for critical Jira issues:** Collaborate in channels for critical issues and invite your team to collaborate on its resolution. - **Jira issues on your fingertips:** List your open issues, and search them using filters or JQL through Slack. - **Planning poker:** Achieve accuracy and uniformity in estimating task complexity across your projects by engaging in collaborative estimation sessions with your team. ## How to get started 1. Click Add to Slack 2. Connect to your Jira instance. 3. Set up your Jira project and create webhooks. Create triggers for webhook and issue-related activities in Jira. 4. Configure 2 Slack channels: One for issue notifications and another for reporting issues. Additionally, you can initiate Planning Poker sessions within your team by using the **"Create Planning Poker Game"** workflow. This collaborative estimation technique fosters precise and consistent task complexity estimates among team members. Put an end to constantly checking your e-mail or logging into Jira. Reduce the time spent switching between Jira and Slack to help your team focus on work with Jira Software Slack integration!

Workflows

Resolve the issue when ✅ emoji is added in project channels

This workflow resolves the issue when ✅ emoji is added to a message in the selected project channels.

Sync comments coming from project channel

This workflow synchronizes messages posted in the project channel with Jira issue comments.

Send messages to Slack channels

This workflow sends issue details to the project channel, report issue channel, and a dedicated channel.

Change status

Run this workflow to change the status of an issue in Jira.

My open issues

Run this workflow to see open issues assigned to you.

Assign issue

Run this workflow to assign an issue to a user in Jira.

Create Planning poker game

Run this workflow to create a Planning poker game.

Send thread messages to Slack channels

This workflow sends issue updates about issues as threaded messages to the project channel, report issue channel, and dedicated channel.

Create an issue when 🎫 emoji is added

This workflow creates a new issue when 🎫 emoji is added to an issue post in selected channels during the setup.

Search issues using JQL

Run this workflow to search Jira issues using JQL.

Set final estimation

This workflow enables you to set final estimation to an issue in the Planning poker game.

Notify channels when an issue is created

This workflow sends notifications to the project channel, report issue channel, and a dedicated channel whenever an issue is created.

Update issue

Run this workflow to update a Jira issue.

Notify channels when an issue is updated

This workflow sends notifications to the project channel, report issue channel, and a dedicated channel whenever an issue is updated.

Link issues

Run this workflow to link Jira issues.

Set up your Jira project and create webhooks in Jira

This workflow creates a webhook for the Jira project you select. Then creates two Slack channels; one to receive the selected Jira project notifications, the other to automatically create Jira issues by adding a ticket emoji.

Find Slack user

This workflow finds the Slack user ID from the Jira account ID or user email.

Listen Jira events

This workflow listens to events coming from Jira and triggers the relevant actions based on those events.

Get the status of an issue when a message is sent

This workflow allows you to get the status of the issue when a message is posted.

Add comment to the Jira issue when 📌 emoji is added in report issue channels

This workflow adds a comment to the Jira issue when the 📌 emoji is added under the issue thread in project channels.

Report an issue

Run this workflow to create a new issue in Jira.

Configure personal notifications

This workflow lets users choose when and how they receive issue notifications.

Search issues by filters

Run this workflow to search Jira issues using filters.

Comment on an issue

Run this workflow to add a comment to an issue in Jira.

Send direct messages to users

This workflow sends direct messages to users, sharing issue details and updates with the assignee, watchers, and reporters

View issue details

Run this workflow to view issue details.

Assign the issue when the 👀 emoji is added in report issue channels

This workflow assigns the issue to the user who added the eyes 👀 emoji in the selected report issue channels.

Create a dedicated channel

This workflow creates a dedicated channel for issues with a critical label or highest priority.

Add issues with JQL

This workflow adds Jira issues that meet certain rules you set using Jira Query Language (JQL) to a Planning poker game.

Add comment to the issue

This workflow adds a comment to an issue.

Archive the dedicated channel when issue is deleted

This workflow archives the dedicated channel when a critical Jira issue is deleted.

Delete webhooks

This workflow deletes selected webhooks.

Add issues

This workflow adds Jira issues to the corresponding Planning poker game.

Watch issue

Run this workflow to add yourself as a watcher to a Jira issue.

Create issue

Run this workflow to create a new issue in Jira.

Send direct message when comment is added

This workflow sends a direct message to the issue related users whenever a comment is added to an issue.

Notify channels when a comment is added

This workflow sends notifications to the project channel, report issue channel, and a dedicated channel whenever a comment is added to the issue.

Convert Slack mentions to Jira mentions

This workflow converts Slack mentions to Jira mentions.

Notify channels when an issue is deleted

This workflow sends notifications to the project channel, report issue channel, and a dedicated channel when an issue is deleted.

Send direct message when work log is added to an issue

This workflow sends a direct message to users as soon as a work log is added to an issue.

Refresh webhook

This workflow is automatically run to extend the expiration date of the webhook in Jira.

Convert Jira mentions to Slack mentions

This workflow converts Jira mentions to Slack mentions.

Configure channels for Jira notifications

This workflow creates webhook and issue-related triggers in your Jira account. And also selects which Jira project will send notifications to which Slack channel.

Send attachment to channel

This workflow sends the attachments to the channel

Get channel configurations

This workflow retrieves channel configurations.

Resolve the issue when ✅ emoji is added in report issue channels

This workflow resolves the issue when ✅ emoji is added to a message in the selected report issue channels.

Assign the issue when the 👀 emoji is added in project channels

This workflow assigns the issue to the user who added the eyes 👀 emoji in the selected project channels.

Send direct message

This workflow sends issue details to a user.

Acquire lock

This workflow locks an issue for issue updates.

Log work to an issue

Run this workflow to log work to an issue in Jira.

Configure channels to report a Jira issue

This workflow runs when a ticket 🎫 emoji is added to a message in this channel, users are prompted to create a new issue in Jira. You can also check your issue's status by mentioning your issue.

Add comment to the Jira issue when 📌 emoji is added in project channels

This workflow adds a comment to the Jira issue when the 📌 emoji is added under the issue thread in project channels.

Send message to channel

This workflow sends a message to the channel when there's an issue creation, update, or a new comment is added.

Sync comments coming from report issue channel

This workflow synchronizes messages posted in the issue report channel with Jira issue comments.

Upload attachments

This workflow uploads the attachments.

Poker game created event listener

This workflow listens to the event coming from the Planning poker app when a game is added to the "Games" table.

Notify channels when work log is added to an issue

This workflow sends notifications to the project channel, report issue channel, and a dedicated channel whenever a work log is added to an issue.

Jira log work reminder

Sends direct messages to the users for the issues that are in progress of the active sprints.

Convert Jira markdown to Slack markdown

This workflow transforms Jira markdown into Slack markdown.

Get issue from issue table

This workflow retrieves issue details from the Issue table based on message timestamps.

Add comment to the Jira issue when 📌 emoji is added in DM

This workflow adds a comment to the Jira issue when the 📌 emoji is added under the issue thread in project channels.

Listen planning poker game created event

This workflow runs when a Planning poker game is created.

Send direct message when an issue is created

This workflow sends a direct message to the necessary team members as soon as a new issue is created.

Send direct message when an issue is updated

This workflow sends a direct message whenever there's an update to an issue.

Security & Compliance

Privacy & data governance

Data retention policy

For the most up to date policy information, always refer to: https://actioner.com/privacy-policy , https://actioner.com/gdpr and https://actioner.com/security. How long we keep your data prior to the deletion of data or termination of the contract between the customer and Actioner depends on the type of data, as described in further detail below:

Account data: Personal data that relates to customers’ relationship with the Actioner, including your workspace details, user accounts and your billing information. We retain your account information for as long as your account is active. We also retain some of your information as necessary to comply with our legal obligations, to resolve disputes, to enforce our agreements, to support business operations, and to continue to develop and improve our Services. Where we retain information for Service improvement and development, we take steps to eliminate information that directly identifies you, and we only use the information to uncover collective insights about the use of our Services, not to specifically analyze personal characteristics about you.

Configuration data: Any configuration or personal data that is required by Actioner to be functional for the customer, such as (a) applications and their sub-configurations like workflows, documents or functions, (b) credentials, connections and integrations with the third party providers, (c) identity and access management related personal data. Actioner stores and processes configuration data for the permitted purposes until the customer elects to delete such configuration data via the service and the customer is solely responsible for deleting configuration data.

Usage data: (a) Inputs, requests and form data provided by the end users or clients of the customer, (b) any data that is programmatically, periodically or automatically received through an integration of the customer, (c) any content stored as a result of processing a configuration data, (d) activity logs used to identify the source of service requests. Actioner deletes any stored usage Data sixty (60) days after the data is produced.

Data archiving and removal policy

For the most up to date policy information, always refer to: https://actioner.com/privacy-policy , https://actioner.com/gdpr and https://actioner.com/security. Whenever a user account is deleted by a workspace admin, Actioner automatically deletes all data stored within the context of the deleted user account like profile information and the credentials / connections for the third party integrations. Whenever an app is deleted by an app admin, Actioner automatically deletes all data stored within the context of the app like tables, records, workflow, docs, files, etc. Whenever the workspace deletion is initiated by a workspace admin, Actioner automatically deletes all data stored within the context of workspace after a waiting period of 72 hours. After the waiting period, the deletion may take up to 10 days after the termination effective date. When any data is deleted, the archived copy of the data on Actioner’s backup systems will remain for 30 days and the backup data will be securely isolated and protected from any further processing, except as otherwise required by applicable law or regulation.

Data storage policy

At Actioner, ensuring the security of our users' data is paramount. To this end, we employ robust cryptography policies and practices. All data stored within our systems is encrypted at rest using the AES256 encryption standard, providing an additional layer of protection against unauthorized access. Furthermore, we uphold strict encryption standards for data in transit, both within our internal networks and over public channels. All data transmissions utilize TLS1.2 or higher encryption protocols, safeguarding information from interception or tampering. In terms of cryptographic key management, we rely on the AWS Key Management Service (KMS) for secure and controlled handling of cryptographic keys. This includes secure key generation, restricted access, secure storage, regular backups, and periodic rotation of keys. Our integration with AWS services streamlines the encryption process and enhances control over access to keys, thereby bolstering the overall security of our platform.We operate a comprehensive backup program at Actioner. This includes our internal systems, where our backup measures are designed in line with system recovery requirements. With respect to our cloud services, and specifically referring to you and your application data, we also have extensive backup measures in place. Our data backups are retained for 30 days with support for point-in-time recovery and are encrypted using AES-256 encryption.

Data center location(s)

United States

Data hosting details

Actioner is a cloud-native product whose infrastructure is hosted on industry-leading cloud provider Amazon Web Services (AWS). Actioner cloud services and data are hosted on Amazon Web Services (AWS). Where all our computing, messaging, network, and storage layers are located in the US West, our browser application is distributed via our CDN network all over the world. As a design standard, all Actioner services as well as the upstream computing, messaging, network and storage services are running on multiple availability zones (AZs) so that the traffic and the data are distributed among them. This design allows us to tolerate zone-specific failures with no downtime. This multi-zone high availability is the first line of defense for geographic and environmental risks and means that services running in multi-AZ deployments should be able to withstand AZ failure.