Atlassian’s Jira has become a standard for managing large software projects in many companies. Many of those same companies also use GitHub as their source code repository and, unsurprisingly, there has long been an official way to integrate the two. That old way, however, was often slow, limited in its capabilities and unable to cope […]
Atlassian’s Jira has become a standard for managing large software projects in many companies. Many of those same companies also use GitHub as their source code repository and, unsurprisingly, there has long been an official way to integrate the two. That old way, however, was often slow, limited in its capabilities and unable to cope with the large code bases that many enterprises now manage on GitHub .
Almost as if to prove that GitHub remains committed to an open ecosystem, even after the Microsoft acquisition, the company today announced a new and improved integration between the two products.
“Working with Atlassian on the Jira integration was really important for us,” GitHub’s director of ecosystem engineering Kyle Daigle told me ahead of the announcement. “Because we want to make sure that our developer customers are getting the best experience of our open platform that they can have, regardless of what tools they use.”
So a couple of months ago, the team decided to build its own Jira integration from the ground up, and it’s committed to maintaining and improving it over time. As Daigle noted, the improvements here include better performance and a better user experience.
The new integration now also makes it easier to view all the pull requests, commits and branches from GitHub that are associated with a Jira issue, search for issues based on information from GitHub and see the status of the development work right in Jira, too. And because changes in GitHub trigger an update to Jira, too, that data should remain up to date at all times.
The old Jira integration over the so-called Jira DVCS connector will be deprecated and GitHub will start prompting existing users to do the upgrade over the next few weeks. The new integration is now a GitHub app, so that also comes with all of the security features the platform has to offer.
Maybe you’ve never heard about Tiny, but chances are, you’ve used its products. Tiny is the company behind the text editors you’ve likely used in WordPress, Marketo, Zendesk, Atlassian and other products. The company is actually the result of the merger of Moxiecode, the two-person team behind the open source TinyMCE editor, and Ephox, the […]
Maybe you’ve never heard about Tiny, but chances are, you’ve used its products. Tiny is the company behind the text editors you’ve likely used in WordPress, Marketo, Zendesk, Atlassian and other products. The company is actually the result of the merger of Moxiecode, the two-person team behind the open source TinyMCE editor, and Ephox, the company behind the Textbox.io editor. Ephox was the larger company in this deal, but TinyMCE had a significantly larger user base, so Tiny’s focus is now almost exclusively on that.
And the future of Tiny looks bright thanks to a $4 million funding round led by BlueRun Ventures, the company announced today (in addition to a number of new products). Tiny CEO Andrew Roberts told me the round mostly came together thanks to personal connections. While both Ephox and Moxiecode were profitable, now seemed like the right time to try to push for growth.
Roberts also noted that the merger itself is a sign of the company’s ambitions. “I think we’ve always been searching for how we could get that hockey stick growth to kick in,” he said. “I don’t think we would’ve done the merger if we weren’t hungry for that next level of success. So after two or three years [after the merger], we started to feel like we had the signs of a business that could grow into something significant and big and with some good numbers behind it. So were: ‘alright, now is the time.'”
While Tiny continues to offer its free open-source editor, it offers a cloud-hosted version of its service with a fee based on the number of users for developers who want the company to handle the backend infrastructure, as well as a self-hosted version that Tiny charges for based on the number of servers it runs on.
Roberts noted that quite a few developers try to build their own text editors. Yet handling all the edge cases and ensuring compatibility is actually quite hard. He estimates that it would take two or three years to build a new text editor from the ground up.
As part of today’s announcement, Tiny is also launching a number of new products. The most important of those from a business perspective is surely Tiny Drive, a file storage service that developers can integrate with the TinyMCE editor. Tiny Drive offers all of the file storage features that one would expect, including the ability to handle images and other assets. Tiny Drive uses AWS’s S3 file storage service and CloudFront CDN to distribute files.
Also new is the Tiny App Directory, which Roberts likened to the Slack App Directory. The idea here is to offer a curated list of TinyMCE plugins. For now, there is no revenue sharing here or any other advanced features, but it’s definitely a play for creating a larger ecosystem around the editor.
Tiny also today announced the first developer preview of the TinyMCE 5 editor. The updated editor features a new user interface that gives the editor a more modern look. Developers can customize it to their hearts’ content, with plenty of compatible plugins and advanced features to extend the editor based on their specific needs. There’s also now an emoticon plugin.
Talking about customized editors: You’re probably aware of WordPress’ efforts to modernize its text editor. The new editor, called Gutenberg, focuses more on page building than the current one, but as Roberts stressed, the underlying rich text editor is still based on the TinyMCE libraries. He noted that even the classic version, though, was always a subset of TinyMCE’s editor. What’s maybe even more important for Tiny as a company, though, is that none of WordPress’ changes will influence its business, even though WordPress and TinyMCE have long had what he describes as a “symbiotic relationship.”
“Tiny’s core business comes from a mix of software vendors, large enterprises, and agencies building custom solutions for clients that has little to do with the WordPress ecosystem,” he notes. “It is a popular and commercially viable project in its own right.”
Anaxi‘s mission is to bring more transparency to the software development process. The tool, which is now live for iOS, with web and Android versions planned for the near future, connects to GitHub to give you actionable insights about the state of your projects and manage your projects and issues. Support for Atlassian’s Jira is […]
Anaxi‘s mission is to bring more transparency to the software development process. The tool, which is now live for iOS, with web and Android versions planned for the near future, connects to GitHub to give you actionable insights about the state of your projects and manage your projects and issues. Support for Atlassian’s Jira is also in the works.
The new company was founded by former Apple engineering manager and Docker EVP of product development Marc Verstaen and former CodinGame CEO John Lafleur. Unsurprisingly, this new tool is all about fixing the issues these two have seen in their daily lives as developers.
“I’ve been doing software for 40 years,” Verstaen told me.” And every time is the same. You start with a small team and it’s fine. Then you grow and you don’t know what’s going on. It’s a black box.” While the rest of the business world now focuses on data and analytics, software development never quite reached that point. Verstaen argues that this was acceptable until 10 or 15 years ago because only software companies were doing software. But now that every company is becoming a software company, that’s not acceptable anymore.
Using Anaxi, you can easily see all issue reports and pull requests from your GitHub repositories, both public and private. But you also get visual status indicators that tell you when a project has too many blockers, for example, as well as the ability to define your own labels. You also can define due dates for issues.
One interesting aspect of Anaxi is that it doesn’t store all of this information on your phone or on a proprietary server. Instead, it only caches as little information as necessary (including your handles) and then pulls the rest of the information from GitHub as needed. That cache is encrypted on the phone, but for the most part, Anaxi simply relies on the GitHub API to pull in data when needed. There’s a bit of a trade-off here in terms of speed, but Verstaen noted that this also means you always get the most recent data and that GitHub’s API is quite fast and easy to work with.
The service is currently available for free. The company plans to introduce pricing plans in the future, with prices based on the number of developers that use the product inside a company.
Atlassian today announced the first beta of a new edition of its flagship Jira project and issue tracking tool that is meant to help ops teams handle incidents faster and more efficiently. Jira Ops integrates with tools like OpsGenie, PagerDuty, xMatters, Statuspage, Slack and others. Many teams already use these tools when their services go […]
Atlassian today announced the first beta of a new edition of its flagship Jira project and issue tracking tool that is meant to help ops teams handle incidents faster and more efficiently.
Jira Ops integrates with tools like OpsGenie, PagerDuty, xMatters, Statuspage, Slack and others. Many teams already use these tools when their services go down, but Atlassian argues that most companies currently use a rather ad hoc approach to working with them. Jira Ops aims to be the glue that keeps everybody on the same page and provides visibility into ongoing incidents.
This is obviously not the first time Atlassian is using Jira to branch out from its core developer audience. Jira Service Desk and Jira Core, for example, aim at a far broader audience. Ops, however, goes after a very specific vertical.
“Service Desk was the first step,” Jens Schumacher, Head of Software Teams at Atlassian, told me. And we were looking at what are the other verticals that we can attack with Jira.” Schumacher also noted that Atlassian built a lot of tools for its internal ops teams over the years to glue together all the different pieces that are necessary to track and manage incidents. With Jira Ops, the company is essentially turning its own playbook into a product.
In a way, though, using Jira Ops adds yet another piece to the puzzle. Schumacher, however, argues that the idea here is to have a single place to manage the process. “The is that when an incident happens, you have a central place where you can go, where you can find out everything about the incident,” he said. “You can see who has been paged and alerted; you can alert more people if you need to right from there; you know what Slack channel the incident is being discussed in.”
Unlike some of Atlassian’s other products, the company doesn’t currently have any plans to launch a self-hosted version of Jira Ops. The argument here is pretty straightforward: if your infrastructure goes down, then Jira Opes could also go do down — and then you don’t have a tool for managing that downtime.
Jira Ops is now available for free for early access beta users. The company expects to launch version 1.0 in early 2019. By then Atlassian will surely also have figured out a pricing plan, something it didn’t announce today.
InVision today announced a newly expanded integration and strategic partnership with Atlassian that will let users of Confluence, Trello and Jira see and share InVision prototypes from within those programs. Atlassian’s product suite is built around making product teams faster and more efficient. These tools streamline and organize communication so developers and designers can focus […]
InVision today announced a newly expanded integration and strategic partnership with Atlassian that will let users of Confluence, Trello and Jira see and share InVision prototypes from within those programs.
Atlassian’s product suite is built around making product teams faster and more efficient. These tools streamline and organize communication so developers and designers can focus on getting the job done. Meanwhile, InVision’s collaboration platform has caught on to the idea that design is now a team sport, letting designers, engineers, executives and other shareholders be involved in the design process right from the get-go.
Given the way design and development teams use both product suites, it only makes sense to let these product suites communicate with one another.
As part of the partnership, Atlassian has also made a strategic financial investment in InVision, though the companies declined to share the amount.
Here’s what InVision CEO Clark Valberg had to say about it in a prepared statement:
In today’s digital world creating delightful, highly effective customer experiences has become a central business imperative for every company in the world. InVision and Atlassian represent the essential platforms for organizations looking to unleash the potential of their design and development teams. We’re looking forward to all the opportunities to deepen our relationship on both a product and strategic basis, and build toward a more cohesive digital product operating system that enables every organization to build better products, faster.
InVision has been working to position itself as the Salesforce of the design world. Alongside InVision and InVision Studio, the company has also built out an asset and app store, as well as launched a small fund to invest in design startups. In short, InVision wants the design ecosystem to revolve around it.
Considering that InVision has raised more than $200 million, and serves 4 million users, including 80 percent of the Fortune 500, it would seem that the strategy is paying off.
When a couple of long-established players are competing hard in any given market, one easy way to expand that market is to simply combine forces. That’s what SmartBear Software did today when it bought Zephyr, a fellow software testing firm with deep reach into the Atlassian Marketplace. Terms of the deal were not disclosed. Zephyr […]
When a couple of long-established players are competing hard in any given market, one easy way to expand that market is to simply combine forces. That’s what SmartBear Software did today when it bought Zephyr, a fellow software testing firm with deep reach into the Atlassian Marketplace. Terms of the deal were not disclosed.
Zephyr gives SmartBear a tool that includes Zephyr for Jira. Jira is the popular issue tracking software from Atlassian favored by many developers. In fact, Zephyr is the top grossing app in the Atlassian Marketplace, boasting over 18,000 teams using the tool to execute over 40 million tests, according to information supplied by the company.
That kind of reach appealed to SmartBear CEO Justin Teague. The company claims the combined organizations will give them one of the most complete software testing product portfolios in the market. “The acquisition of Zephyr will establish SmartBear as a leader in test management and broaden our portfolio of high-impact, easy-to- use tools…,” he said in a statement.
For Zephyr, getting acquired gives them increased reach as a combined company that they simply couldn’t build on their own. “By leveraging the industry expertise and array of SmartBear solutions, our customers will continue to benefit from the tools they know and love, while now being able to solve additional software development challenges related to building, testing, and monitoring software applications across the UI and API layer,” Zephyr CEO Scott Johnson said in a statement. (In other words, their existing customers should have nothing to worry about after the transition.)
SmartBear launched in 2009 and was acquired by Francisco Partners, a private equity firm in May 2017. Leveraging additional players in a market to build more substantial marketshare is a typical private equity strategy after acquiring a company. It’s the two companies are better than one approach.
Zephyr launched in 2007 and has raised $31 million. Investors include Frontier Ventures, Cervin Ventures and WTI.
Firebase is now Google’s default platform for app developers, and over the course of the last four years since it was acquired, the service has greatly expanded its feature set and integrations with Google services. Today, it’s rolling out yet another batch of updates that bring new features, deeper integrations and a few design updates […]
Firebase is now Google’s default platform for app developers, and over the course of the last four years since it was acquired, the service has greatly expanded its feature set and integrations with Google services. Today, it’s rolling out yet another batch of updates that bring new features, deeper integrations and a few design updates to the service.
The highlight of this release is the launch of in-app messaging, which will allow developers to send targeted and contextual messages to users as they use the app. Developers can customize the look and feel of these in-app notifications, which are rolling out today, but what’s maybe even more important is that this feature is integrated with Firebase Predictions and Google Analytics for Firebase so that developers can just react to current behavior but also Firebase’s predictions of how likely a user is to spend some additional money or stop using the app.
Developers who use Atlassian’s JIRA will also be happy to hear that Firebase is launching an integration with this tool. Firebase users can now create JIRA issues based on crash reports in Firebase. This integration will roll out in the next few weeks.
Another new integration is a deeper connection to Crashlytics, which Google acquired from Twitter in 2017 (together with Fabric). Firebase will now let you export this data to BigQuery to analyze it — and then visualize it in Google’s Data Studio. And once it’s in BigQuery, it’s your data, so you’re not dependent on Firebase’s retention and deletion defaults.
Talking about reports, Firebase Cloud Messaging is getting a new reporting dashboard and the Firebase Console’s Project Overview page has received a full design overhaul that’ll allow you to see the health and status of your apps on a single page. The Latest Release section now also features live data. These features will start rolling out today and should become available to everybody in the next few weeks.
Firebase Hosting, the service’s web content hosting service, is also getting a small update and now allows you to host multiple websites within one project. And when you push an update, Firebase Hosting now only uploads the files that have changed between releases, which should speed up that process quite a bit.
Hello and welcome back to Equity, TechCrunch’s venture capital-focused podcast where we unpack the numbers behind the headlines. This week Matthew Lynley and Alex Wilhelm were joined by 500 Startups CEO Christine Tsai for what turned out to be a super packed episode. We kicked off with the latest from Slack: $400 million new dollars at a shiny, […]
Hello and welcome back to Equity, TechCrunch’s venture capital-focused podcast where we unpack the numbers behind the headlines.
We kicked off with the latest from Slack: $400 million new dollars at a shiny, new $7 billion valuation, according to TechCrunch. The new capital comes after the firm raised a huge sum last year from SoftBank’s Vision Fund.
We dug into why the company would raise again, and what competitors it has left after the Atlassian deal.
Next up, two earnings reports. Continuing our tradition of keeping tabs on recent tech IPOs, we talked through Snap and Dropbox which reported earnings this week. Both lost ground after doing so. Ironically, they each beat financial expectations.
Snap ended up dropping value over a DAU decline, and Dropbox’s fall is still a bit undetermined. But by the time this episode ships, perhaps the market will have figured it out.
Next up we scrolled through the key reviews of the commercially available Magic Leap headset that is out at last. It’s a bit pricey, and a bit not-what-people-expected, but the well-funded startup seems to have avoided a complete miss. Its second-generation device may prove to be more impactful.
With today’s announcement from Atlassian that it was selling to Slack the IP assets of its two enterprise communications tools, HipChat and Stride, it closes the book on one of the earliest competitors in the modern enterprise chat space. It also was a clear signal that Slack is not afraid to take on its giant […]
With today’s announcement from Atlassian that it was selling to Slack the IP assets of its two enterprise communications tools, HipChat and Stride, it closes the book on one of the earliest competitors in the modern enterprise chat space. It also was a clear signal that Slack is not afraid to take on its giant competitors by forming key alliances.
That the announcement came from Slack co-founder and CEO Stewart Butterfield on Twitter only exacerbated that fact. Atlassian has a set of popular developer tools like Jira, Confluence and Bitbucket. At this point, HipChat and Stride had really become superfluous to the company and they sold the IP to their competitor.
Not only is Slack buying the assets and Atlassian is effectively shutting down these products, Atlassian is also investing in Slack, a move that shows it’s throwing its financial weight behind the company, as well, and forming an alliance with them.
Slack has been burning it up since in launched in 2014 with just 16,000 daily active users. At last count, in May, the company was reporting 8 million active users, 3 million of which were paid. That’s up from 6 million DAUs and 2 million paid users in September 2017. At the time, the company was reporting $200 million in annual recurring revenue. It’s a fair bet with the number of paid users growing by one-third at last count, that revenue number has increased significantly, as well.
Slack and products of its ilk like Workplace by Facebook, Google Hangouts and Microsoft Teams are trying to revolutionize the way we communicate and collaborate inside organizations. Slack has managed to advance the idea of enterprise communications that began in the early 2000s with chat clients, advanced to Enterprise 2.0 tools like Yammer and Jive in the mid-2000s and finally evolved into modern tools like Slack we are using today in the mobile-cloud era.
Slack has been able to succeed so well in business because it does much more than provide a channel to communicate. It has built a platform on top of which companies can plug in an assortment of tools they are using every day to do their jobs, like ServiceNow for help desk tickets, Salesforce for CRM and marketing data and Zendesk for customer service information.
This ability to provide a simple way to do all of your business in one place without a lot of task switching has been a Holy Grail of sorts in the enterprise for years. The two previously mentioned iterations, chat clients and Enterprise 2.0 tools, tried and failed to achieve this, but Slack has managed to create this single platform and made it easy for companies to integrate services.
This has been automated even further by the use of bots, which can act as trusted assistants inside of Slack, providing additional information and performing tasks for you on your behalf when it makes sense.
Slack has an otherworldly valuation of more than $5 billion right now, and is on its way to an eventual IPO. Atlassian might have thrown in the towel on enterprise communications, but it has opened the door to getting a piece of that IPO action while giving its customers what they want and forming a strong bond with Slack.
Others like Facebook and Microsoft also have a strong presence in this space and continue to build out their products. It’s not as though anyone else is showing signs of throwing up their hands just yet. In fact, just today Facebook bought Redkix to enhance its offering by giving users the ability to collaborate via email or the Workplace by Facebook interface, but Atlassian’s acquiescence is a strong signal that if you had any doubt, Slack is a leader here — and they got a big boost with today’s announcement.
Hipchat, the workplace chat app that held the throne before Slack was Slack, is being discontinued. Also being discontinued is Atlassian’s own would-be Hipchat replacement, Stride. News of the discontinuation comes first not from Atlassian, but instead from a somewhat surprising source: Slack CEO Stewart Butterfield. In a series of tweets, Butterfield says that Slack […]
Hipchat, the workplace chat app that held the throne before Slack was Slack, is being discontinued. Also being discontinued is Atlassian’s own would-be Hipchat replacement, Stride.
News of the discontinuation comes first not from Atlassian, but instead from a somewhat surprising source: Slack CEO Stewart Butterfield. In a series of tweets, Butterfield says that Slack is purchasing the IP to “better support those users who choose to migrate” to its platform.
Butterfield also notes that Atlassian will be making a “small but symbolically important investment” — likely a good move, given that rumors of a Slack IPO have been swirling (though Butterfield says it won’t happen this year). Getting a pre-investment IPO into Slack might end up paying off for Atlassian better than trying to continue competing.
The deal we’re announcing today with Atlassian is pretty amazing. Indeed, I tried to fit it all in one (280 character) tweet but I just couldn’t do it. So, I’ll lay it out in a few. But first, I wanted to thank Scott, Mike, Jay and the team: incredible to work with you.
There are several components, all aligned around cementing the partnership and, most importantly, taking some big steps together to drive fundamental improvements in the experience of the millions of people around the world who are using our products together every single day.
Details: • Atlassian is discontinuing Hipchat/Stride • Slack is purchasing the IP to better support those users who choose to migrate • We’re both working closely together to make sure that’s as simple and painless a process as possible …
Atlassian VP of Product Management, Joff Redfern, confirmed the news in a blog post, calling it the “best way forward” for its existing customers. It’s about as real of an example of “if you can’t beat’em, join’em” as you can get; even Atlassian’s own employees will be moved over to using Slack.
It doesn’t sound like any of Atlassian’s other products will be affected here; Bitbucket, Jira, etc will carry on, with only the company’s real-time communications platforms being shuttered.