Software teams can now easily implement development best practices and world-class project tracking at the same time. JIRA 6.3 is more tightly integrated with Stash and Bitbucket for teams using Git and Crucible for teams using Subversion, Perforce, and Mercurial. JIRA automatically updates issues the moment development of an issue is complete. We’ve also enhanced reporting in JIRA Agile to give the entire team an end to end view of the project allowing for more data-driven decisions. Combined with automatic issue transitions, data is now more accurate than ever before. Adding issues, versions, and components are now one click operations. Discover the fully integrated development workflow with the new JIRA 6.3.
Truly intelligent issue tracking
JIRA 6.3 enables development teams to do more as JIRA is more capable than ever. Product owners, developers, team leads, and every member of your software team can now spend more time on what matters and less time managing issues. Developers thrive when they’re writing code and JIRA 6.3 frees development teams to do exactly that. Developers can create a branch right from the issue and JIRA automatically maintains the issue status throughout the dev lifecycle. You’re probably thinking, what’s new here? JIRA already has smart commits. Smart commits require that developers know insider commands like: [cc]JRA-345 #resolve #time 2d 5h #comment Task completed ahead of schedule[/cc] JIRA 6.3 blows smart commits out of the water. When developers create a pull request or code review to flag code for the team’s attention, JIRA automatically updates the related issue’s status. Teams can use a new workflow component called a trigger to update issues as the development team works. Smart commits work alongside the new automatic transitioning to automate time tracking, commenting and more!
The addition of automatic transitions in JIRA ensures a smoother development cadence and saves our development team valuable hours. Less time managing issues means more time for coding and building great products.
Nate Van Dusen, Engineering Program Management Director, Trulia
Let’s dig in a bit more. When a developer creates a pull request or a code review, JIRA can automatically transition the linked issue from In Progress to Code Review. Developers don’t have to update both systems.
We’ve created triggers that mirror many developer actions: create branch, commit created, as well as various pull request and review events. Teams rely on JIRA for its flexible workflow engine. Triggers are additive to your team’s existing workflow. Configure the right actions to automate your development process. We call it “just enough process.” We don’t want to force your team into a prescriptive workflow and we’ve built triggers to allow you to tighten your team’s process.
When teams use automatic transitions everyone stays in the loop. Development managers, team leads, and product owners can look in one place and see up-to-date status for an issue. With the development panel from JIRA 6.2 all of the development artifacts are in one place. Up-to-the-minute and accurate status has never been this automated or visible.
Drive more informed decisions
JIRA Agile 6.5 ships alongside JIRA 6.3. New reports in JIRA Agile make interpreting agile metrics easier than ever before. The smarter JIRA not only keeps issues up to date it learns how your team plans, works, and ships product. We’ve released three updated reports: release burndown, epic burndown, and the control chart. The release and epic burndown charts make understanding work over time simple. Teams can easily see work completed, scope added, scope removed, and a forecast for when the release or epic will be complete.
Agile is all about learning and optimizing through change. The new control chart gives deep insight into the flow of work through the team. Teams can learn where bottlenecks lay to increase the team’s velocity. The control chart also helps teams make better estimates which leads to more predictable deliveries.
It’s easy to zoom in on a period of time to further understand the data. Long-running issues can easily be targeted, broken down, and understood.
Easily create issues
Customers have asked us for an easy way to create issues inside of sprints as the team works. JIRA 6.3 with JIRA Agile adds in-line issue create inside of plan mode. As the team engages in sprint planning, new tasks arise. Conversations often arise during these meetings that is critical to capture in the moment. Recording issues inline ensures that new work is clearly defined. This is a good thing as work becomes more defined and predictable. Simply add new work to a future sprint in one click with our new in-line issue create.
And that’s not all
There’s even more inside JIRA 6.3. We made it easier for administrators to add components and versions to a JIRA project. Just type the new version or component name right inside the issue detail screen.
We’ve also updated the way users attach assets to JIRA tickets. With an all new HTML5 interface, just drag your attachments onto the JIRA issue for easy upload. JIRA 6.3 includes new features like enhanced auditing, new issue importers to make migration easier, and a new permission option to more flexibly control who can transition issues. The release notes have all the details to get you started!
Untangle your development process with JIRA
JIRA 6.3 and JIRA Agile 6.5 make development clearer and also minimize interruptions inside of the team. Automatic issue transitioning keeps issues up-to-date as developers write code. Enhanced reports inside of JIRA Agile make key agile metrics easier to understand driving better development decisions across the team. Features like in-line issue create make tracking and delivering work easier than ever.
New to JIRA?
Get up and running in a matter of minutes with a free JIRA Cloud trial.
Ready to upgrade?
Check out the full release notes and start seeing real results with JIRA 6.3 today. Cloud Customers: Congrats! You’ve have been auto-upgraded to JIRA 6.3!