JIRA 6.3: Easy Development

It is now possible for software teams to implement development best practices and world-class project tracking at the same time without hassle. JIRA 6.3 is now more integrated with Stash and Crucible. The moment the development of an issue is complete, JIRA automatically updates the issues. In addition, JIRA Agile now allows the entire team an end to end view of the project through enhanced reporting decisions.

You are currently viewing a placeholder content from Youtube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.

More Information

JIRA 6.3 lets developers create a branch right from the issue and JIRA automatically keeps up with the issue status during the dev lifecycle without the need to use smart commits. JIRA automatically updates the issue’s status, when developers create a pull request or code review to flag code for the team’s attention. The new workflow tool called trigger updates issues while the development team is doing their work. Smart commits work alongside the new automatic transitioning to automate time tracking, commenting and more!
Due to these new features, JIRA guarantees a smoother workflow and saves the development team some time that can be invested in coding.

Let’s see in detail: By creating a pull request or a code review JIRA automatically changes the linked issues from In Progress to Code Review. Atlassian has created a variety of triggers that reflect many actions taken by developers such as create branch, commit, pull requests, and review events. Additionally, you can configure the right actions needed for your development process.

The advantage are clear: Everyone stays up to date - with just one look at the development panel - all in one place.


JIRA Agile 6.5 goes hand in hand with JIRA 6.3. It features new reports, helping you to interpret the current work status easier than ever before. The updated reports are: release burndown, epic turndown 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.


The new control chart gives a more elaborated view of the teams workflow. It helps the team to estimate the process better and make more predictable deliveries.


Another great feature of JIRA 6.3: in-line issue create inside of sprints. It is not only time efficient but also ensures all new work is being defined. And even more: Attachments can now easily uploaded by dragging them onto the JIRA issue, supported by an all new HTML5 interface. Atlassian has also added enhanced auditing, new issue importers to enable an easier migration and a new permission option controlling issue transitions more flexible.

More information can be found in Atlassian's release notes.

Read more about JIRA here:
JIRA Workflows: Convert tasks into systematic and transparent procedures
Are Trello and Basecamp JIRA Alternatives?
Tempo Planner for JIRA: Agile capacity and resource scheduling, team and project management, business data for teams
SWIFT: The Easiest and Fastet Way to Try Confluence, JIRA or Stash

Forget Less and Ensure Quality with didit Checklists for Atlassian Cloud Forget Less and Ensure Quality with didit Checklists for Atlassian Cloud Forget Less and Ensure Quality with didit Checklists for Atlassian Cloud
Our blog articles reflect the situation at the time of writing and are not updated. It is therefore possible that the contents are outdated and no longer correspond to the latest developments. We do not accept any liability for this.

Leave a Reply