Actioner brings **Bitbucket pull request management** to Slack and boosts the productivity of DevOps teams by giving them the right tools to collaborate on PRs. Get alerted of open PRs, merge them faster, track their lifecycle through dedicated Slack channels, and automatically sync PR comments with conversations — all within Slack. Actioner brings all the informative context to smart notifications and allows your teams to take action without leaving Slack. Improve your code reviews by putting an end to going back and forth between your tools and increase engagement by managing your PR review process in Slack.
### Features
- Collaborate on single-purpose Slack channels that are dedicated to each PR on connected repositories. Channel gets archived when the PR is closed.
- Track pipeline runs in one place through ephemeral PR channels.
- Get notified of comments added to Bitbucket PR and easily turn relative Slack messages into PR comments by emojis.
- Broadcast commit events to the main branch through dedicated Slack channels.
### How it works
Actioner connects to your Bitbucket & Slack and brings the best of pull request management to your teams. You can get notified of open PRs in your repos, the ones assigned to you, or the ones that you’re added as a reviewer in Slack. Actioner also allows your teams to track changes on main branches by broadcasting new commits in Slack.
Most importantly, Actioner creates ephemeral Slack channels to review PRs, invites assignees and reviewers to this channel, and lets them collaborate to deliver faster and better code reviews. Your teams can track completed pipeline runs and the comments added to the PR in Bitbucket. They can easily turn conversations into comments by adding emojis to their Slack messages. When the PR is closed, the temp channel gets archived but stays accessible whenever your teams need to re-check any review.
Workflows
Create pull request channel
This workflow automatically creates a dedicated Slack channel when a pull request is opened.
Send message when PR is merged
This workflow automatically sends a message to the merge request Slack channel when it is merged. Also, it notifies the PR owner with a direct message.
Notify channel when a commit is pushed to default branch
This workflow sends a message to the preselected main/master branch updates Slack channel when a new commit is pushed.
Archive channel when PR is closed
When a PR is closed or merged, this workflow sends a message that the channel will be archived and archives the Slack channel of the PR.
Approve pull request
Run this workflow to approve a pull request.
Subscribe to Bitbucket Events
This workflow creates a webhook on Bitbucket to subscribe to the pull request events from a selected repository. If you want to subscribe to events from multiple repositories, you can re-run this workflow.
Delete branch
This workflow deletes a Bitbucket branch.
Onboard users who joined master push channel
When a user joins to PR updates channel, this workflow sends a direct message to the user from Slack. The message describes how to connect Bitbucket with Actioner and how to use the pull request review app.
Send Message when PR Comment is added
This workflow automatically sends a message to the PR's dedicated Slack channel when someone posts a comment.
Add comment to pull request with pin emoji
This workflow is triggered when the pin emoji is put on a message in a dedicated pull request channel. The message content is automatically added to the pull request as a comment.
List open pull requests
This workflow lists the open pull requests on Bitbucket.
Archive PR channel
This workflow archives the given Slack channel.
Send message when PR is approved
This workflow automatically sends a message to the dedicated Slack channel when the PR is approved.
Send message when pipeline hook is received
Sends a thread message whenever a pipeline associated with a PR is completed.
Merge pull request
Run this workflow to merge a Bitbucket pull request.
Set PR update channel
This workflow creates a channel on Slack with a given prefix. (#-bitbucket-main-pushes) Anyone who joins this channel will receive an onboarding message from Actioner to explain how to connect GitHub. Also, when a commit is pushed to the main branch, a message will be sent to this channel to notify your team.
Comment on a pull request
Run this workflow to add a comment on a Bitbucket pull request.
Send message when changes requested
This workflow automatically sends a message to the PR's dedicated Slack channel when someone requests changes on the PR. Also, PR owner is notified with a direct message.
Invite pull request reviewers to PR channel
This workflow invites pull request reviewers to the PR channel.
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.
Data hosting company
Amazon Web Services (AWS)
App/service has sub-processors
Yes
Guidelines for sub-processors
Certifications & compliance
SOC attestation
Privacy policy
GDPR commitment
Data deletion request procedure
Security
Supports Single Sign On (SSO) with the following providers
Google, Slack, Okta
Supports Security Assertion Markup Language (SAML)
No
Has a dedicated security team
Yes
Contact for security issues
Has a vulnerability disclosure program
Yes
Vulnerability disclosure program URL
Vulnerability disclosure program covers Slack app
Yes
Has a bug bounty program
Yes
Bug bounty program URL
Requires third party authorization/connections
No
Third party services used by this app
Uses token rotation
No
Contributors
Actioner
.png){kind=spacer}
