Personal blog of Yzmir Ramirez

Every company wants to maintain that initial spark it had when it was an early stage startup, but keeping that going as you scale into a public company isn’t always easy. Atlassian is taking a unique approach by opening up product ideas to an internal competition, and actually funding and building the best ones with the goal of bringing them to market.

Steve Goldsmith, who is heading up the project for Atlassian says that it’s an in-house startup incubator called Point A. The company wants to encourage employees to be constantly thinking about new ways to improve the products. And every employee is encouraged to participate, not just engineers or product managers, as my might think.

“Point A is our internal framework for turning ideas into products. It’s our way of finding the innovation that’s happening all over the company, and giving a process and framework for those ideas to reach the maturity of actually becoming products that we offer to our customers,” Goldsmith told me.

He says that like many companies they hold internal hackathons and other events where many times employees come up with creative concepts for products, but they tend to get put on a shelf after the event is over and never get looked at again. With Point A, they can actually compete to put their experiments to work and see if they are actually viable.

“So we think of Point A as a way of finding all those different ideas and prototypes and concepts that people have in their brains or on the side of their desk kind of thing, and giving a process and a structure for those ideas to get out the door, and really invest in the ones that have some traction,” Goldsmith said.

He says by providing an official internal process to vet and maybe fund some of them, people inside the organization know that their proposals are being heard and they have a mechanism for submitting them, and the company has a way of seeing them.

The company launched Point A in 2019 looking at 35 possible projects, and testing them as possible products. Last January, they chose 9 that made the final cut and 4 turned into actual products and made it out the door this week including the Jira Work Management tool, which is being released today.

The next program is ready to roll with employees ready to present their ideas in a pitch day competition to get things going. “Our first class is graduating out of this program, and […] we start the process again. We actually just went through our big list of all the ideas to do it a second time, and we are doing a pitch day. It’s going t be a fun Shark Tank, The Voice kind of inspired [competition],” he said.

Company co-founders and co-CEOs Mike Cannon-Brookes and Scott Farquhar both participate in judging the competition, so it has executive buy-in giving more clout to the program and sending a message to employees that their ideas are being taken seriously.

The company provides funding, time away from your regular job, executive coaches and combines that with customer collaboration and early founder involvement with the goal of finding a scalable, repeatable process with defined phases that helps teams take the most innovative ideas from concept to customer.

Some make it. Some don’t as you might expect, but so far the plan seems to be working and is successfully encouraging innovation from within, something every company should be trying to do.

Atlassian today announced a new edition of its Jira project management tool, Jira Work Management. The company has long been on a journey of bringing Jira to teams beyond the software development groups it started out with. With Jira Service Management, it is successfully doing that with IT teams. With Jira Core, it also moved further in this direction, but Jira Work Management takes this a step further (and will replace Jira Core). The idea here is to offer a version of Jira that enables teams across marketing, HR, finance, design and other groups to manage their work and — if needed — connect it to that of a company’s development teams.

“Jira Software’s this de-facto standard,” Atlassian’s VP of Product Noah Wasmer told me. “We’re making just huge inroads with Jira Service Management right now, bringing IT teams into that loop. We have over 100,000 customers now on those two products. So it’s really doing incredibly well. But one of the things that CIOs say is that it’s really tough to put Jira Software in front of an HR team and the legal team. They often ask, what is code? What is a pull request?”

Image Credits: Atlassian

Wasmer also noted that even though Jira Software is specifically meant for developers, about half of its users are already in other teams that work with these development teams. “We think that [Jira Work Management] gives them the more contextually relevant tool — a tool that actually helps them accelerate and move faster,” Wasmer said.

With Jira Work Management, the company is looking at making it easier for any team to track and manage their work in what Wasmer described as a “universal system and family of product.” As company’s look at how to do remote and hybrid work, Atlassian believes that they’ll need this kind of core product to keep track of the work that is being done. But it’s also about the simple fact that every business is now a software business and while every team’s work touches upon this, marketing and design teams often still work in their own silos.

Image Credits: Atlassian

These different teams, though, also have quite different expectations of the user interface they need to manage their work most effectively. So while Jira Work Management features all of the automation features and privacy controls of its brethren, it is based around a slightly different and simplified user interface than Jira Software, for example.

What’s even more important, though, is that Jira Work Management offers a variety of views for teams to enter and manipulate their data. To get new users onboarded quickly, Atlassian built a set of templates for some of the most common use cases it expects, though users are obviously free to customize all these different views to their hearts’ — and business needs’ — content.

Atlassian also changed some of the language around Jira tickets. There are no “stories” and “bugs” in Jira Work Management (unless you add them yourself) and instead, these templates use words like “tasks,” “assets” (for design use cases) or “candidates” (for HR).

Image Credits: Atlassian

Given the fact that spreadsheets are the universal language of business, it’s maybe no surprise that the List view is core here, with an Excel/Airtable-like experience that should immediately feel familiar to any business user. It’s inline editable and completely abstracts away the usual Jira ticket, even though underneath, it’s the same taxonomy and infrastructure.

“We really wanted people to walk into this product and just understand that there is work that needs to be done,” Chase Wilson, the head of product marketing for Jira Work Management, said. He noted that the team worked on making the experience feel snappy.

Image Credits: Atlassian

The other views available are pretty straightforward: a calendar and Gantt chart-like timeline view, as well as the traditional Kanban board that has long been at the core of Jira (and Agile in general).

Jira Work Management also lets users build forms, using a drag-and-drop editor that makes it easy for anybody inside an organization to build forms and collect requests that way. Only a few weeks ago, Atlassian announced the acquisition of ThinkTilt, the company behind the popular no-code form-builder ProForma and it looks like it is already putting this acquisition to work here.

As Wasmer stressed, Jira Work Management is meant to help different teams get work done in a way that works best for them. But because Jira is now a family of products, it also enables a lot more cross-team collaboration. That means a development team that is working on implementing a GDPR requirement can now build a workflow that ties in with the project board for a legal team that then allows legal to hold up a software release until it approves this new feature.

“We hear about this all the time today,” he said. “They just stick the legal team into Jira Software — and it over-inundates them with information that’s not relevant to what they’re trying to get done. Now we can expose them. And we also then get that legal team, that marketing team, exposed to different templates for different work. What they’re finding is that once they get used to it for that must-do use case, they start saying: Well, hey, why don’t I use this for contract approvals at the end of the quarter?”

Image Credits: Atlassian

As for pricing, Atlassian follows its same standard template here, offering a free tier for teams with up to 10 users and then the paid tiers start at $5/user/month, with discounts for larger teams.

Looking ahead, Atlassian plans to add more reporting capabilities, native approvals for faster signoffs and more advanced functionality across the new work views.

It’s worth noting that Jira Work Management is the first product to come out of Point A, Atlassian’s new innovation program “dedicated to connecting early-adopter customers with product teams to build the next generation of teamwork tools.”

Confluence, Atlassian’s wiki-like collaborative workspace, has been around for more than 15 years, and is often a core knowledge-sharing tool for the companies that implement it. But for the most part, Confluence is a business tool and looks like it, with walls of text and the occasional graph, table or image. But user expectations have changed, and so it’s maybe no major surprise that Atlassian is now bringing a stronger emphasis on design to the service.

Today’s update, for example, brings to the service features like cover images, title emojis and customizable space avatars (that is, “icons that denote a ‘space’ or section of Confluence”). The team also recently introduced smart links, which allow you to paste links from services like YouTube and Trello and have the service immediately recognize them and display them in their native format. Other new features include the ability to schedule when a new page is published and the ability to convert pages to blog posts (because, as it turns out, Atlassian has seen a bit of a resurgence in corporate blogging — mostly for internal audiences — during the pandemic).

Image Credits: Atlassian

“We ended up doing something that we called ‘love sprint,’ where we prioritize about 30 features for the enhancements, which are all — if you think about the themes — about how you design information in this world where you have to read more, where you have to write more,” Natalia Baryshnikova, the head Of Product Management for Atlassian’s Confluence Experience Group, told me. “And there’s the attention span that’s kind of pushing its limits. So how do you design for that situation? How do you discover our content?”

Baryshnikova tells me that the team took a close look at how content production, management and delivery works in the social media world. But some of the new features are also purely a reaction to a changing work environment. Take the ability to schedule when pages are published, for example. Employees who work from home may work especially late or early right now, for example, in order to prioritize childcare. But they still want the content they produce to be seen inside the company, and that can be hard when you would otherwise publish it at 11 p.m., for example.

Image Credits: Atlassian

And having your content get noticed is getting harder because Confluence usage has dramatically increased in the last 12 months. As Atlassian noted today, more than 60,000 companies are now using the service. And inside those companies, those users are also far more active than ever before. The number of Confluence pages created from March 2020 to March 2021 increased by more than 33%. The average user now creates 11% more pages, but the product’s superusers have often doubled or tripled their output.

The use of Confluence has also helped many companies reduce their number of meetings, but as Baryshnikova noted, “not only are pages competing with meetings — but pages are competing with pages.” So using good graphics, for example, is a way for a user’s content to stand out in the noise of corporate content production. Which, I have to admit, strikes me as a somewhat strange dynamic. But I guess that just like on the web, in order to stand out in a corporate environment, you have to make the documents you produce stand out in order to get noticed. Maybe that — as well as the lack of watercooler conversations — is also the reason corporate blogging is seeing an uptick right now.

The Atlassian platform is chock full of data about how a company operates and communicates. Atlassian launched a machine learning layer, which relies on data on the platform with the addition of Atlassian Smarts last fall. Today the company announced it was acquiring Chartio to add a new data analysis and visualization component to the Atlassian family of products. The companies did not share a purchase price.

The company plans to incorporate Chartio technology across the platform, starting with Jira. Before being acquired, Chartio has generated its share of data, reporting that 280,000 users have created 10.5 million charts for 540,000 dashboards pulled from over 100,000 data sources.

Atlassian sees Chartio as way to bring that data visualization component to the platform and really take advantage of the data locked inside its products. “Atlassian products are home to a treasure trove of data, and our goal is to unleash the power of this data so our customers can go beyond out-of-the-box reports and truly customize analytics to meet the needs of their organization,” Zoe Ghani, head of product experience at platform at Atlassian wrote in a blog post announcing the deal.

Chartio co-founder and CEO Dave Fowler wrote in a blog post on his company website that the two companies started discussing a deal late last year, which culminated in today’s announcement. As is often the case in these deals, he is arguing that his company will be better off as part of large organization like Atlassian with its vast resources than it would have been by remaining stand-alone.

“While we’ve been proudly independent for years, the opportunity to team up our technology with Atlassian’s platform and massive reach was incredibly compelling. Their product-led go to market, customer focus and educational marketing have always been aspirational for us,” Fowler wrote.

As for Chartio customers unfortunately, according to a notice on the company website, the product is going to be going away next year, but customers will have plenty of time to export the data to another tool. The notice includes a link to instructions on how to do this.

Chartio was founded in 2010, and participated in the Y Combinator Summer 2010 cohort. It raised a modest $8.03 million along the way, according to Pitchbook data.

Atlassian has made it clear for some time that it’s all in on the cloud, but now it’s official. The company stopped selling new on-prem server licenses as of yesterday. Perhaps to take away the sting of that move for large organizations, today it announced a new all-inclusive enterprise pricing tier.

Atlassian chief revenue officer Cameron Deatsch says that previously the company had offered a free tier and then standard and premium level paid tiers. “And now this cloud Enterprise Edition will be our highest tier, and what this will allow is for the most complex deployments, the largest customers who need unlimited scale, the customers that have all the security and regulatory requirements, data residency, you name it, — that is what we’re launching starting [today],” Deatsch told me.

What the enterprise tier delivers is unlimited instances across the Atlassian product line for each enterprise customer. That means a big company with multiple divisions could, for instance, have 20 instances of Jira and Confluence deployed with one for each division and a central management console.

While the company is supporting existing on-prem server customers until 2024, the idea is to now move them to the cloud and this offering should help. One thing we have clearly seen is that the pandemic has accelerated the move to the cloud by companies of every size, and this should encourage the company’s largest customers to make the move.

“The reality is, the demand was there, which was great to see, but we actually had this huge pipeline of our largest customers, basically trying to build their plan over the next couple of years to get to our cloud. The general availability of our Enterprise Edition is going to accelerate that even more,” he said.

It’s a move the company has been working towards for some time, but it really began to take shape when they shifted their operations to AWS and rebuilt the entire stack as a set of microservices beginning in 2016. This was the first step towards being able to handle the increased kinds of workloads an enterprise tier would require.

The company reported earnings at the end of last month with revenue of $501.4 million up 23% YoY with over 11,000 net new subscribers, a record for the company. The new enterprise tier won’t help with new customer volume, but it should help with overall revenue as more customers look for cloud solutions and pricing that meets their needs.

As a product manager, I’m a true believer that you can solve any problem with the right product and process, even one as gnarly as the multiheaded hydra that is microservice overhead.

Working for Vertex Ventures US this summer was my chance to put this to the test. After interviewing 30+ industry experts from a diverse set of companies — Facebook, Fannie Mae, Confluent, Salesforce and more — and hosting a webinar with the co-founders of PagerDuty, LaunchDarkly and OpsLevel, we were able to answer three main questions:

1. How do teams adopt microservices?
2. What are the main challenges organizations face?
3. Which strategies, processes and tools do companies use to overcome these challenges?

How do teams adopt microservices?

Out of dozens of companies we spoke with, only two had not yet started their journey to microservices, but both were actively considering it. Industry trends mirror this as well. In an O’Reilly survey of 1500+ respondents, more than 75% had started to adopt microservices.

It’s rare for companies to start building with microservices from the ground up. Of the companies we spoke with, only one had done so. Some startups, such as LaunchDarkly, plan to build their infrastructure using microservices, but turned to a monolith once they realized the high cost of overhead.

“We were spending more time effectively building and operating a system for distributed systems versus actually building our own services so we pulled back hard,” said John Kodumal, CTO and co-founder of LaunchDarkly.

“As an example, the things we were trying to do in mesosphere, they were impossible,” he said. “We couldn’t do any logging. Zero downtime deploys were impossible. There were so many bugs in the infrastructure and we were spending so much time debugging the basic things that we weren’t building our own service.”

As a result, it’s more common for companies to start with a monolith and move to microservices to scale their infrastructure with their organization. Once a company reaches ~30 developers, most begin decentralizing control by moving to a microservice architecture.

Large companies with established monoliths are keen to move to microservices, but costs are high and the transition can take years. Atlassian’s platform infrastructure is in microservices, but legacy monoliths in Jira and Confluence persist despite ongoing decomposition efforts. Large companies often get stuck in this transition. However, a combination of strong, top-down strategy combined with bottoms-up dev team support can help companies, such as Freddie Mac, make substantial progress.

Some startups, like Instacart, first shifted to a modular monolith that allows the code to reside in a single repository while beginning the process of distributing ownership of discrete code functions to relevant teams. This enables them to mitigate the overhead associated with a microservice architecture by balancing the visibility of having a centralized repository and release pipeline with the flexibility of discrete ownership over portions of the codebase.

What challenges do teams face?

Teams may take different routes to arrive at a microservice architecture, but they tend to face a common set of challenges once they get there. John Laban, CEO and co-founder of OpsLevel, which helps teams build and manage microservices told us that “with a distributed or microservices based architecture your teams benefit from being able to move independently from each other, but there are some gotchas to look out for.”

Indeed, the linked O’Reilly chart shows how the top 10 challenges organizations face when adopting microservices are shared by 25%+ of respondents. While we discussed some of the adoption blockers above, feedback from our interviews highlighted issues around managing complexity.

The lack of a coherent definition for a service can cause teams to generate unnecessary overhead by creating too many similar services or spreading related services across different groups. One company we spoke with went down the path of decomposing their monolith and took it too far. Their service definitions were too narrow, and by the time decomposition was complete, they were left with 4,000+ microservices to manage. They then had to backtrack and consolidate down to a more manageable number.

Defining too many services creates unnecessary organizational and technical silos while increasing complexity and overhead. Logging and monitoring must be present on each service, but with ownership spread across different teams, a lack of standardized tooling can create observability headaches. It’s challenging for teams to get a single-pane-of-glass view with too many different interacting systems and services that span the entire architecture.

Atlassian has been offering collaboration tools, often favored by developers and IT for some time with such stalwarts as Jira for help desk tickets, Confluence to organize your work and BitBucket to organize your development deliverables, but what it lacked was a machine learning layer across the platform to help users work smarter within and across the applications in the Atlassian family.

That changed today, when Atlassian announced it has been building that machine learning layer, called Atlassian Smarts, and is releasing several tools that take advantage of it. It’s worth noting that unlike Salesforce, which calls its intelligence layer Einstein or Adobe, which calls its Sensei, Atlassian chose to forgo the cutesy marketing terms and just let the technology stand on its own.

Shihab Hamid, the founder of the Smarts and Machine Learning Team at Atlassian, who has been with the company 14 years, says they avoided a marketing name by design. “I think one of the things that we’re trying to focus on is actually the user experience and so rather than packaging or branding the technology, we’re really about optimizing teamwork,” Hamid told TechCrunch.

Hamid says that the goal of the machine learning layer is to remove the complexity involved with organizing people and information across the platform.

“Simple tasks like finding the right person or the right document becomes a challenge, or at least they slow down productivity and take time away from the creative high-value work that everyone wants to be doing, and teamwork itself is super messy and collaboration is complicated. These are human challenges that don’t really have one right solution,” he said.

He says that Atlassian has decided to solve these problems using machine learning with the goal of speeding up repetitive, time-intensive tasks. Much like Adobe or Salesforce, Atlassian has built this underlying layer of machine smarts, for lack of a better term, that can be distributed across their platform to deliver this kind of machine learning-based functionality wherever it makes sense for the particular product or service.

“We’ve invested in building this functionality directly into the Atlassian platform to bring together IT and development teams to unify work, so the Atlassian flagship products like JIRA and Confluence sit on top of this common platform and benefit from that common functionality across products. And so the idea is if we can build that common predictive capability at the platform layer we can actually proliferate smarts and benefit from the data that we gather across our products,” Hamid said.

The first pieces fit into this vision. For starters, Atlassian is offering a smart search tool that helps users find content across Atlassian tools faster by understanding who you are and how you work. “So by knowing where users work and what they work on, we’re able to proactively provide access to the right documents and accelerate work,” he said.

The second piece is more about collaboration and building teams with the best personnel for a given task. A new tool called predictive user mentions helps Jira and Confluence users find the right people for the job.

“What we’ve done with the Atlassian platform is actually baked in that intelligence, because we know what you work on and who you collaborate with, so we can predict who should be involved and brought into the conversation,” Hamid explained.

Finally, the company announced a tool specifically for Jira users, which bundles together similar sets of help requests and that should lead to faster resolution over doing them manually one at a time.

“We’re soon launching a feature in JIRA Service Desk that allows users to cluster similar tickets together, and operate on them to accelerate IT workflows, and this is done in the background using ML techniques to calculate the similarity of tickets, based on the summary and description, and so on.”

All of this was made possible by the company’s previous shift from mostly on-premises to the cloud and the flexibility that gave them to build new tooling that crosses the entire platform.

Today’s announcements are just the start of what Atlassian hopes will be a slew of new machine learning-fueled features being added to the platform in the coming months and years.

LaunchNotes, a startup founded by the team behind Statuspage (which Atlassian later acquired) and the former head of marketing for Jira, today announced that it has raised a $1.8 million seed round co-led by Cowboy Ventures and Bull City Ventures. In addition, Tim Chen (general partner, Essence Ventures), Eric Wittman (chief growth officer, JLL Technologies), Kamakshi Sivaramakrishnan (VP Product, LinkedIn), Scot Wingo (co-founder and CEO, Spiffy), Lin-Hua Wu (chief communications officer, Dropbox) and Steve Klein (co-founder, Statuspage) are participating in this round.

The general idea behind LaunchNotes is to help businesses communicate their software updates to internal and external customers, something that has become increasingly important as the speed of software developments — and launches — has increased.

In addition to announcing the new funding round, LaunchNotes also today said that it will revamp its free tier to include the ability to communicate updates externally through public embeds as well. Previously, users needed to be on a paid plan to do so. The team also now allows businesses to customize the look and feel of these public streams more and it did away with subscriber limits.

“The reason we’re doing this is largely because [ … ] our long-term goal is to drive this shift in how release communications is done,” LaunchNotes co-founder Jake Brereton told me. “And the easiest way we can do that and get as many teams on board as possible is to lower the barrier to entry. Right now, that barrier to entry is asking users to pay for it.”

As Brereton told me, the company gained about 100 active users since it launched three months ago.

Image Credits: LaunchNotes

“I think, more than anything, our original thesis has been validated much more than I expected,” co-founder and CEO Tyler Davis added. “This problem really does scale with team size and in a very linear way and the interest that we’ve had has largely been on the much larger, enterprise team side. It’s just become very clear that that specific problem — while it is an issue for smaller teams — is much more of a critical problem as you grow and as you scale out into multiple teams and multiple business units.”

It’s maybe no surprise then that many of the next items on the team’s roadmap include features that large companies would want from a tool like this, including integrations with issue trackers, starting with Jira, single sign-on solutions and better team management tools.

“With that initial cohort being on the larger team size and more toward enterprise, issue tracker integration is a natural first step into our integrations platform, because a lot of change status currently lives in all these different tools and all these different processes and LaunchNotes is kind of the layer on top of that,” explained co-founder Tony Ramirez. “There are other integrations with things like feature flagging systems or git tools, where we want LaunchNotes to be the one place where people can go. And for these larger teams, that pain is more acute.”

The fact that LaunchNotes is essentially trying to create a system of record for product teams was also part of what attracted Cowboy Ventures founder Aileen Lee to the company.

Image Credits: LaunchNotes

“One of the things that I thought was kind of exciting is that this is potentially a new system of record for product people to use that kind of lives in different places right now — you might have some of it in Jira and some in Trello, or Asana, and some of that in Sheets and some of it in Airtable or Slack,” she said. She also believes that LaunchNotes will make a useful tool when bringing on new team members or handing off a product to another developer.

She also noted that the founding team, which she believes has the ideal background for building this product, was quite upfront about the fact that it needs to bring more diversity to the company. “They recognized, even in the first meeting, ‘Hey, we understand we’re three guys, and it’s really important to us to actually build out [diversity] on our cap table and in our investing team, but then also in all of our future hires so that we are setting our company up to be able to attract all kinds of people,” she said.

No company is completely insulated from the macroeconomic fallout of COVID-19, but we are seeing some companies fare better than others, especially those providing ways to collaborate online. Count Atlassian in that camp, as it provides a suite of tools focused on working smarter in a digital context.

At a time when many employees are working from home, Atlassian’s product approach sounds like a recipe for a smash hit. But in its latest earnings report, the company detailed slowing growth, not the acceleration we might expect. Looking ahead, it’s predicting more of the same — at least for the short term.

Part of the reason for that — beyond some small-business customers, hit by hard times, moving to its new free tier introduced last March — is the pain associated with moving customers off of older license revenue to more predictable subscription revenue. The company has shown that it is willing to sacrifice short-term growth to accelerate that transition.

We sat down with Atlassian CRO Cameron Deatsch to talk about some of the challenges his company is facing as it navigates through these crazy times. Deatsch pointed out that in spite of the turbulence, and the push to subscriptions, Atlassian is well-positioned with plenty of cash on hand and the ability to make strategic acquisitions when needed, while continuing to expand the recurring-revenue slice of its revenue pie.

The COVID-19 effect

Deatsch told us that Atlassian could not fully escape the pandemic’s impact on business, especially in April and May when many companies felt it. His company saw the biggest impact from smaller businesses, which cut back, moved to a free tier, or in some cases closed their doors. There was no getting away from the market chop that SMBs took during the early stages of COVID, and he said it had an impact on Atlassian’s new customer numbers.

Image Credits: Atlassian

Still, the company believes it will recover from the slow down in new customers, especially as it begins to convert a percentage of its new, free-tier users to paid users down the road. For this quarter it only translated into around 3000 new customers, but Deatsch didn’t seem concerned. “The customer numbers were off, but the overall financials were pretty strong coming out of [fiscal] Q4 if you looked at it. But also the number of people who are trying our products now because of the free tier is way up. We saw a step change when we launched free,” he said.

A lot of “partnerships” between tech companies don’t get very far beyond a press release and maybe some half-hearted co-selling attempts. When Atlassian sold its chat services to Slack in 2018, the two companies said they would form a new partnership and with Atlassian leaving the chat space, a lot of people were skeptical about what that would really mean.

Since then, things got pretty quiet around the collaboration between the two companies, but today the companies announced some of the deep integration work they’ve done, especially within Slack .

Image Credits: Atlassian

Over the course of the last two years, Slack and Atlassian shipped 11 product integrations, which now see about a million active users every month, with Jira being the most often used integration, followed by Halp, which Atlassian acquired earlier this year.

Every month, Atlassian currently sends 42 million Jira notifications to Slack — and that number continues to grow.

At the core of these integrations is the ability to get rich unfurls of deep links to Atlassian products in Slack, no matter whether that’s in DMs, public or private channels. Coming soon, those unfurls will become a default feature within Slack, even if the user who is seeing the link isn’t an Atlassian user yet.

“Today, if you do drop a Jira link in your channel and you’re not a user — or even if you are and you’re not authed in — you just see a link,” Brad Armstrong said.

“You don’t get the benefit of the unfurl. And so one of the things we’re doing is making that unfurl available to everybody, regardless of whether you are logged in and regardless of whether you’re even an Atlassian customer.”

Image Credits: Atlassian

The two companies also worked closely together on making moving between the products easier. If you are a Jira user, for example, you’ll soon be able to click on a link in Slack and if you’re not currently logged into your Atlassian account, you’ll be automatically logged in. The two companies are taking this even further by automatically creating Jira accounts for users when they come from Slack.

“Even if you’re not a user, when you click on the link, we will then map you from Slack and create a Jira user for you that provisions you and auths you in so you’re immediately becoming a Jira user by virtue of wanting to collaborate on that piece of content in Slack,” Armstrong explained.

That, the two companies argue, turns Slack into something akin to a passport that gives you access to the Atlassian product suite — and that should also make onboarding a lot easier for new users.

Image Credits: Atlassian

“As you could probably imagine, as you know, onboarding is a pain, it’s hard because you have different roles, different size teams, so on and so forth,” said Bryant Lee, Atlassian’s head of product partnerships. “And that’s where you see some of the authentication stuff, the unfurling discovery piece really being an understanding of what those practices are. But the way that we look at it is not just about the product but people, products and practices. So it’s really about understanding who it is that we’re trying to optimize for.”

In addition to these new integrations that are launching soon, the two companies are also expanding their co-marketing efforts, starting with a new 50%-off offer for Atlassian users who want to also use Slack.

“We’re building on the strong foundation of our partnership’s success from the past two years, which has yielded tremendous shared customer momentum and impactful product integrations,” said Slack co-founder and CEO Stewart Butterfield . “Thanks to our strategic alliance, Slack and Atlassian have become the technology stack of choice for developer teams.”