Guest blog: Burnup reports for agile teams

Atlassian's public issue tracker, jira.atlassian.com, contains all kinds of feature requests from our customers. Occasionally, our ecosystem of add-on developers takes it upon themselves to build an add-on that implements one of these features, such as Broken Build recently did with GHS-5513. Meet them at Atlassian Summit 2014! “As a Scrum Master, I'd like to have BurnUp Charts available on the Rapid Board” says GHS-5513. What is a burnup chart anyway, and why does it matter? Can't you just

Continue reading »

Confluence tip of the month: shares vs. @mentions

To anyone who doubts that Atlassians are a little too obsessed with collaboration, and tools related thereto, let me describe a recent discussion we had (which took place on our internal Confluence, of course). It was lamented that, when you share a page and include a note, those thoughts are read by one person, then languish forever in their inbox. There’s no clean way to reply to them, and nobody else can benefit from what you had to say. By building the share-by-email feature, had we inadvertently

Continue reading »

What the heck is the quiet period? The quiet period is a optional setting on each repository connected to Bamboo. After seeing that a commit has been made to the repo, the quiet period (if enabled) tells Bamboo how long to wait before actually kicking off the build. It lives under the Advanced options in the Linked Repositories configuration screen. Here's what the configuration looks like: Fun Fact! The quiet period was originally invented to cater for the fact that CVS commits are

Continue reading »

At the heart of every software team is a vibrant culture around creation, organization, and delivery of work. All types of work – be it new features, bugs, spikes… are called 'issues' inside of JIRA. Issues provide a flexible way to organize and distribute work across the team so that everyone remains productive and the whole organization runs at a smooth cadence. This article will focus on three key mistakes teams make and how to correct them when using issues to track work. From feature

Continue reading »

Last week, Tim Pettersen and I held a webinar on optimizing your CI system for Git. We had a great time putting it together, and attendees asked some truly excellent questions, so I think we can safely call this one a success. To sum up, we covered... Why branch-and-merge workflows are so effective (and easier in Git than in SVN, et al) Strategies for reducing build times How to reap the benefits of "pure" CI without piling changes willy-nilly onto a central branch Git hooks that reinforce

Continue reading »

As Git solidifies its position as the version-control-of-choice in the workplace, Stash is delighting those workplace Git users. And it's no surprise: Stash is fantastic for organizing repos, digging into the code, and managing the flow of code from branch to branch. But... If you're not using Bamboo for continuous integration and delivery in combination with Stash, you're not maximizing Stash's full potential. Here's why. Efficient use of time & build resources One thing nearly all

Continue reading »