Slack integration for Jira: Native Bot vs Troopr
Jira Slack integration has grown in popularity with over 1 million monthly active users and 42M monthly notifications delivered from Jira to Slack. : This has validated the need to make it easier for product and engineering teams to manage their Jira projects in Slack. In this blog, we are going to discuss what the native Slack integration for Jira delivers and what are its limitations, and also how it compares to Troopr’s offering.
This blog covers
Overview of major overlapping functionalities and differences (Table)
Overview of functionalities unique to Troopr (Table)
Prime differences in overlapping functionalities
Issue unfurl and search
4. Functionalities unique to Troopr
Access & support
5. Which Jira Slack bot should you choose for your business?
Overview of major overlapping functionalities and differences:
Overview of functionalities unique to Troopr:
Key differences in overlapping functionalities
Issue unfurl and search
Both Troopr and Native integration enables users to quickly create Jira tickets from Slack via buttons and commands.
In addition to this, Troopr Jira bot supports custom fields, including automatic field type discovery and automatic field metadata discovery.
Issue unfurl & search
Both Troopr and Native integration supports issue search via keywords/Jira key and auto unfurl in Slack channels.
Additionally, gathering users feedback - what they needed is simply “reduce context switching”. And that is why we have created a complementary functionality that enables users to take actions on the issues directly in Slack. It is far more efficient as it helps users to save time.
Troopr can notify Jira events both on private and public Slack channels based on different event categories. Individual users are able to receive notifications based on event categories like assigned, mentioned, reported in their private channels. And the team members are able to receive notifications based on event categories say, issue created, assignee changed, issue transitioned, priority updated, issue edited, sprint started/closed in public channels. All of these can be further customized by highly granular filters based on projects, JQL, and delivery frequency.
The default delivery frequency is 1 minute. However users can customize for a longer delivery frequency cycle (upto 8 hours) or even customize for real-time delivery.
All the related events happening in Jira in the same delivery cycle are grouped and delivered to the Slack channels as “one notification”. Correspondingly, all the notification events happening in the same delivery cycle are grouped into “one paginated notification message”.
The above features are in contrast to Native integration that delivers separate Slack notifications on real-time for corresponding Jira actions.
Functionalities unique to Troopr
Besides automatic delivery of grouped and paginated issue lists per delivery cycle, Troopr Jira bot allows users to “pull” the list whenever needed via a simple command. Troopr offers fine filtering by assignee/issue status/JQL. Also, users can switch the issue to edit mode and take any kind of actions on the issues directly from Slack.
This is exactly what is possible with Troopr.
Getting alerts on Slack is great, but working with users - one of the things we have noticed is that they prefer a simple and quicker way to take actions on those alerts. And that is why we have extended this feature on all our notifications/alerts enabling users to take actions on Jira issues (edit/update/modify/add) right from Slack, without opening Jira. Our customers say “This helps them save time in context switching”
This is exactly what is possible with Troopr.
Besides keeping the users informed about Jira events (default and custom) in a grouped and paginated notification message, Troopr Jira bot also supports complex aggregation rules-based notifications.
The key custom rule based notifications include:
Issues not updated in ‘x’ days
Issue missing estimates
All the related events (custom rule based events) happening in the same delivery cycle are grouped and delivered to the Slack channels as “one paginated notification message”, thus ensuring that only one notification message is delivered per custom delivery cycle.
Troopr Jira Slack integration brings Jira reports on daily briefing, project status, burndown chart, and more directly on Slack. Troopr enables users to choose what type of Jira reports they would like to see in Slack. These reports on Slack make it easier for users to trigger contextual discussions on project statuses with the team, surface blockers and keep everyone on the same page, and more.
Key project reports include:
Sprint Burndown Chart
Sprint Velocity Chart
Epic Burndown Chart
Workload pie chart
Issues by Type/Status/Assignee/Priority/Reporter Chart
Issues by Custom JQL
Issues completed recently
Issues progressed recently
Estimates too high in Sprint
Issues missing updates
Issues ready for QA
Issues missing estimate
More on this on another blog.
Troopr’s Jira bot will automatically deliver Jira reports in Slack channels on a recurring basis once users have configured it.
In addition to automatic delivery, users can pull in the reports on demand-basis whenever needed.
Above all, users are also able to deliver stakeholders reports to their Slack chat, even though they do not hold access to Jira account, thus keeping stakeholders informed on the project progress.
Daily Scrum meetings are great. The core idea relies on discussing 3 important aspects: What has been achieved, what have to be done, what are the blockers - if any. Most often, the team members feel it is a distraction to get into the meeting room, gather around, and go ahead with the meeting.
So, we have built a solution around it - Integrated standup in Slack that allows Troopr to asynchronously collect Jira issue updates from project members and automatically update Jira and generate aggregated Standup reports.. Troopr Jira bot invites users on their respective Slack channels with a configured set of questions or Jira issues. At the end of the meeting, the answers are grouped into a report and can be shared on public channels or delivered to individuals privately.
Using Troopr, standup meetings in Slack are highly flexible. Troopr offers shared standup functionalities for users in different organizations (Slack workspaces) to participate in the meetings in shared channels.
Users are also able to run it across different time zones, keeping distributed remote teams on the same page.
Which Jira Slack bot should you choose for your business?
Choosing the right Jira Slack bot for your business depends on the needs of your team.
But the good news is that both Troopr and Native Jira Slack integration are free to try, and you can start by trying it yourself for your business. From there, it is all about determining which integration platform works best for your business.