Atlassian recently released Jira 5 to help foster connections between developers and the rest of the organization. Typically, developers work hard to make great software, Quality Assurance (QA) helps in the quest to find and kill bugs, and Support works with customers who find the ones that slip through the cracks.

In our first deep dive, let’s take a look at some examples of how Jira 5 connects developers and the people they work with every day.

Connecting Development to QA

Rob is the bugmaster working on a development project. Jira has built-in email notifications, so Rob gets notification of new bugs as they come in. He opens this new bug and sends it to QA to investigate.

@mentions in Jira 5 make it easy for the conversation to evolve from there, keeping everything in a central place so anyone looking at this bug knows who is participating and what’s happened so far.

Penny from the QA team discovers this bug is a regression from a previous release, so she increases the priority, and she mentions Scott, the developer working on that feature, in a comment on the bug. Scott is instantly notified and everyone looking at this issue can see that he’s been pulled into the conversation.

 

 

While waiting for a fix, Penny gives the rest of her team a heads up using another new feature in Jira 5: Shares. The Share button lets you send broadcast-style emails to a user in Jira or any email address. Those receiving the email can then decide if they’d like to participate, subscribe to subsequent updates, or just leave it alone.

 

 

 

Connecting Development to Support

While QA and development work hard to keep bugs out of software, Support works with customers who’ve found the few bugs that slipped through. Let’s see how developers connect with support on the same bug.

Scott knows that Tim, a support engineer, has a customer with a related problem. Scott wants Tim to know what’s happening, but Tim doesn’t necessarily need to participate, so Scott uses the Share button to give Tim an update. Tim can then check out the issue to decide if he’d like to follow its progress toward resolution.

Tim wants to dig a bit deeper, so he goes into Jira’s search. He looks for all the issues in the project with certain keywords – ones that might be related to this recent regression – then further refines that to look for just issues that have been Reopened.

project = “Angry Nerds” AND summary ~ “entry field” AND status was “Reopened”

 

Once Tim has come up with a short list of issues that might cause problems for customers, he shares this search with the rest of his team and back with Scott, to make sure everyone is on the same page.

Shares and Mentions in Jira 5 keep the development, QA and support teams all on the same page while getting to the bottom of this Blocker regression bug, but the story doesn’t end here. Stay tuned in the coming weeks for more deep dives about how Jira 5 connects people, activity and applications to help you make great software!

Check out Jira 5

 

Fresh ideas, announcements, and inspiration for your team, delivered weekly.

Subscribe now