JIRA and Confluence
First Release: 2002
Latest Release: 6.2
Interesting Facts: JIRA is used for issue tracking and project management by over 25,000 customers in 122 countries around the globe. That’s a lot of issues!
First Release: 2004
Latest Release: 5.5
Interesting Facts: Confluence dropped wiki markup support in version 4, but geek pressure brought it back as a plugin which provides XHTML-based source markup.
JIRA is an issue tracker that provides issue management, workflows, task assignment, and much more. Confluence is a collaboration tool used to create content and share across a team, with support for tracking requirements, retrospectives and more. JIRA and Confluence are not the only products Atlassian makes, but we put them together here because they are both Atlassian products are designed to work in conjunction.
With JIRA and Confluence, Atlassian has become one of the first coder-centric companies to branch into the mainstream, giving non-technical folks in technical environments a chance to understand WTF is going on. With the exception of Skype, developers are using Confluence even before other tools *actually intended* for communication.
JIRA is far and away the most used issue tracking tool used by modern developers, with an adoption of 57% in our Developer Productivity Report 2013. Runner up GitHub landed in second place place at 21.7% with others being spread below 10% each. It also has an positive effect on the predictability of software delivery, as the same report shows, JIRA users having an increase of 2% in predictability of software delivery. Confluence on the other hand, a content and collaboration tool, is used by 29.7% of respondents as a communication tool if you can believe it, with Skype the only tool to beat it. But with a 3% increase in predictability of software releases, it made the cool list.
In the next 5-10 years, I see companies embracing tools that people actually want to use. It’s totally backwards that people use better software at home than they do at work. Historically, we’ve seen strong JIRA and Confluence adoption among software development teams and internal IT teams, but more and more we’re seeing non-technical teams using our tools to accomplish their most important work. Regarding JIRA’s success, it’s always been driven by its breadth of functionality and accessible price point. As we’ve worked over the years to improve JIRA’s user experience, design, and integrations with other Atlassian products, it has become more ever more popular among teams of all types and sizes. Confluence owes a lot of its success to the success of JIRA. Software development and IT teams typically seek JIRA to manage their projects first, and then seek Confluence to collaborate around technical documentation and other valuable content. In cases where teams are using both tools it is important to them that relevant information is is always up-to-date, easy to find, and at their fingertips without context switching.
– RYAN ANDERSON, Product Marketing Manager for Confluence