Atlassian just announced the availability of a major new release, JIRA 5. The Flowdock plugin is already compatible with it, and as a much-requested update it now shows a more detailed issue change log.
Last year was great for many agile development teams using Atlassian’s products: Confluence’s new rich text editor makes it by far the most usable wiki platform, and hosted Atlassian OnDemand (as evolved from JIRA Studio) is a simple way to get access to JIRA and Confluence.
Last year we also launched the first iterations of our JIRA, Confluence, BitBucket and Bamboo integrations. It made us the only group chat based collaboration app, that works perfectly together with all Atlassian’s major products.
As we keep improving the integrations, your feedback is valuable. Please let us know if you can think of a use case that we currently don’t support!
Atlassian’s issue and project tracking tool, JIRA, has one of the most popular Flowdock integrations. Flowdock adds real-time internal discussions to JIRA and turns actions in tickets into parts of the ongoing conversation in Flowdock.
Here’s a quick 45-second video showcasing the integration.
Atlassian is now launching Atlassian OnDemand. They’re moving their entire product suite to the cloud. Whether you’re looking for hosted issue tracking, agile planning, an enterprise wiki, or source control, they’ve got you covered. Atlassian OnDemand features fully-integrated cloud-based versions of all their most popular development tools to help take you from concept to launch.
Atlassian OnDemand also adds Google Apps integration to Atlassian’s products. Amongst the integration features is logging in with your Google Apps account. Since Flowdock already has the support for it, you can get true single sing-on for all three services.
Atlassian’s Confluence is the most popular enterprise wiki out there, and for good reason. We’re long-time Confluence users here at the Flowdock team as well, which is why Flowdock is now adding a communication layer to your Confluence wiki.
Traditionally, what happens in Confluence, stays in Confluence. Not anymore. Now you can make wiki editing part of the conversation by pushing the changes into Flowdock. Your team will be able to follow wiki edits where the action is: in their flow.
Enterprise wikis do not have to be places where good ideas go to die! Those ideas need to be talked about, they need to be in the center of things and people. They cannot be buried in cluttered email inboxes and the dusty corners of enterprise wikis. They have to be broadcasted to Flowdock!
When Confluence changes are pushed to Flowdock, you get two major, major advantages:
When you make a wiki change, add information, create something new, the fact that you did so, is instantly broadcasted to your team members talking in Flowock so they become aware of it.
Whatever change is made is instantly reviewed by your colleagues. You can talk about the change and decide on further changes, which will again be instantly broadcasted to the Flowdock flow.
This is what a wiki with a working communication layer looks like: