4 reasons why companies use Jira and Slack together
Sick of email? Slack and Atlassian join forces to make it a thing of the past. You already use Jira. You may already use Slack. But are you using them together?
Leading companies like Classpass, HubSpot, Twitter, IBM, and NASA use Jira and Slack at the core of their processes to deliver amazing products. Jira boosts their productivity by letting teams organize, track, and manage work with the flexibility to fit their own workflows. Slack breaks down communication silos via real-time chat conversations in channels, where all discussion and files for a project live in one place.
Jira and Slack have a simple integration to make the value of Jira and Slack together greater than the value of their parts.
We’ve talked to customers, heard your feedback, and are here to share four reasons companies are now picking up Jira and Slack together:
1. They waste less time in their email inboxes.
Many of the work apps and software solutions we depend on today still rely on email to send critical work-related notifications. We are forced back into inboxes just to stay up to date with what’s going on. Without proper settings and tools, one could wake up to hundreds of work related notifications, making it difficult to prioritize and take action. Information overload, anyone?
We’ve seen from actively using Slack at Atlassian, and having talked to numerous customers, that once teams start using Jira and Slack together, they vastly reduce their dependence on email. Some teams have ditched email entirely. One customer, Cimpress, used the integration to get to Inbox 0:
“[The main benefit is] keeping up with our projects and tickets without having to sift through a flood of emails.” - Lead Engineer @ Cimpress
By using the Jira Cloud for Slack integration, tech teams can get their work-critical Jira notifications pushed straight to a dedicated section in Slack, instead of sifting through email to find them. They can control the noise by only surfacing issues they care about with built-in filters with dimensions like, “whether they’re watching”, “mentioned on”, “assigned to”, or “reporter.”
Some teams are testing moving all communications from various services into Slack (including Jira). Bringing multiple conversations to one place has helped teams stay ahead, adapt, and innovate ways of working.
2. Remote teams are using chat to collaborate more than ever before.
Teams are increasingly leaning on chat to collaborate remotely, especially with peers working in multiple time zones and locations. The Jira for Slack integration makes these conversations relevant and actionable.
Every day, we see teams send chat links to Jira issues to reference a body of work. For example, the team below is tracking a piece of work represented in Jira called “Allow users to check out in one click,” represented by the Jira issue reference “DI-6”.
Unfortunately, when teams share raw links to issues, they lose the context that we see above in Jira - the summary, description, assignee, etc. This forces the receivers of links to click on them, leave the context of the conversation, jump into Jira to gain context, then come back to Slack to discuss next steps.
What does DI-6 even mean?
But, teams that use Jira and Slack together can leverage the integration to unlock issue previews and skip the song and dance of going from chat to Jira to gain context. Whenever a Jira issue link or reference is sent into Slack, the integration automatically shows the key details of the issue. That way, receivers of Jira links don’t have to context switch as they can already see the meaning behind the link. Instead, they can dive straight into a meaningful work conversation.
3. They spend less time giving status updates- instead, updates happen automatically.
When teams use Jira and Slack together, they eliminate the need to constantly ask for / give status updates. Instead of having to answer “What’s the status on this piece of work?” all the time, Jira can automatically pipe the status of their work into a channel in Slack – keeping all of the members of the team aligned and up to date.
Below is an example of a channel I created for project DI on the left hand side below “Testing.” On the right hand side, the Jira integration for Slack updates the entire channel regarding the updates of each deliverable, from actions taken in Jira.
No need to ask, “Have you fixed user profile pictures yet?” The integration automatically updates the whole team.
Worried about noise? Teams can always use the integration's simple yet powerful filtering rules to only get messaged about what's important.
4. Less technical teams love creating Jira tickets in Slack- it’s as easy as sending a message.
The Jira for Slack integration provides an incredibly simple way to get managers, execs, and tech-adjacent teams to adopt and collaborate in Jira. Less technical teams can create Jira issues for tech teams to review right from a Slack thread, where they are already engaged.
There are several ways to set this up according to your workflow. For instance, a product manager can queue all incoming requests from their leadership team by simply setting up a Jira board for, “Leadership Asks” and a corresponding Slack channel: #leadsplanning. From there, anyone in the channel can submit a ticket, without ever going into Jira. It's as easy as sending a message.
Teams anywhere can break down silos between technical and non-technical teams with the Jira for Slack integration.
Getting started with Jira and Slack
Not using Jira and Slack together yet? Right now, it’s easier than ever to get started, give them a try together and let us know what you think!
- Install the Jira for Slack integration today!
- Don’t have Slack yet? Get started with Slack today.
- Interested in 50% off Slack Standard or Plus for a year? Learn more about getting 50% off of Slack.
Was this helpful?
Thanks!
David Michelson
7 comments