Documentation for JIRA 6.4. Not using this? See below:
(JIRA 6.3.x documentation | JIRA Cloud documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

Accelerate your teams

JIRA 6.3 helps your teams work more effectively and efficiently
In JIRA 6.3, we've introduced several key concepts and features to ensure that this version of JIRA is the most robust and efficient yet. With JIRA Data Center, we have improved availability for mission critical instances. Our Github importer, inline version and component creation, and auditing options make JIRA easier to administer. And your teams will be more productive with features like inline issue creation and streamlined user interface.

We're still working on further JIRA integration with your favorite Atlassian coding tools, and further improvements to your team's visibility and control of their code is coming soon! Watch this page....

JIRA 6.3 Upgrade Notes

High availability now available with JIRA Data Center

We've built upon all the features that make JIRA great for your business at scale and created a new offering specifically for organizations that require high availability for mission critical JIRA instances. These features are enabled through the clustering capability in JIRA Data Center 6.3:

  • High availability - Active-active clustering of JIRA means minimal downtime for your teams. In addition, replication of the index across each node means that you're safe from data loss due to corruption
  • Scalability - It's easy to scale your JIRA environment as your business grows; simply add another node to maintain the performance required by your business
  • Performance - You can use any form of load-balancing technology – hardware or software – to intelligently distribute load across your Data Center cluster

You can access these features in JIRA 6.3 by purchasing a JIRA Data Center license. Read more about JIRA Data Center here...

Create issues in the moment...

Sitting in a planning meeting and want to create an issue in the moment? Easy! With inline issue creation and JIRA Agile, you can now create an issue from within your Scrum board during planning. Simply click on the Create issue link, select the issue type and enter a brief summary, then hit the Enter button. The issue is created and automatically added to your backlog. It couldn't be simpler!

Learn more...

'On the fly' version and component creation

Project administrators can now add versions and components from within the Fix Version/sAffected Version/s and Component/s fields. Previously, project administrators needed to add a version or component via the appropriate screen on the project's administration page. Now, project administrators are able to create a version or component by typing it in the appropriate field, and selecting it from the drop-down list. When you begin typing text that JIRA does not recognize as existing, it will add it to the bottom of the drop-down list and add (New Version) or (New Component). Selecting the new version or component will automatically create it within your project for future use.

Enhanced auditing capabilities

We first introduced the audit log in JIRA 6.1 late last year. In this release, we've added some new features to the audit log to make it more efficient and easier to use:

  • When a role is removed (deleted) from JIRA, previously the audit log would log an event for every project that it was removed from. Now, the audit log will only log the event that the role has been removed from JIRA.
  • We have given administrators the option to hide logged events from external user directories, such as LDAP and Crowd. These events are still recorded, just hidden from view, and are still available for export and through the REST API.

Increased data import options

The newly released GitHub importer allows you to connect to your GitHub account, regardless of whether it's a private or enterprise account, and import any public, private or starred repository configurations into JIRA. You can map the GitHub labels to issue types, to resolutions, or import them as JIRA labels. The import process supports importing attachments, and also provides you with a detailed log of your import so that you can troubleshoot any issues.

Learn more...

And more!

Of course, that's not all we've done in this release! We've been working hard to improve the user experience, and to make sure that whatever Atlassian product you use, you recognize that great Atlassian "feel".

 Click here to read more about JIRA 6.3 features..
  • Consistency across products - To further align JIRA with our other products, we've changed the Create issue button to simply Create and the Quick Search bar to Search.

  • Transition permission - JIRA now has a new Transition Issues project permission that gives administrators more control over what users can do in JIRA.

  • HTML5 Attachment support - JIRA now supports image capture and attachment using HTML5 in supported browsers.
  • Updates to Admin screen - We've made some minor changes to the location of some of the JIRA administration features. The functionality of the features hasn't changed, but we believe their new location will make them more intuitive to find.

     Click here to see what features we've moved, and where to!
    FeatureNow located in
    Roles administration consoleSystem tab in a new "Security" section
    Global permissions administration consoleSystem tab in a new "Security" section
    Default user preferences administration consoleSystem tab in the "User interface" section
    Shared filters administration consoleSystem tab in a new "User-created assets" section
    Shared dashboards administration consoleSystem tab in a new "User-created assets" section



 Click here to read an important end of support announcement...

Atlassian will stop releasing WAR distribution of JIRA in JIRA 7.0. Please see End of Support Announcements for JIRA for a full list of end of support announcements.

The JIRA 6.3 team


Adam Jakubowski
Aleksander Mierzwicki
Andreas Knecht
Andrew Swan
Antoine Büsch
Arkadiusz Głowacki
Ben Sayers
Ben Wong
Brad Baker
Bradley Ayers
Brenden Bain
Brydie McCoy
Charles O'Farrell
Chris Darroch
Chris Doble
Chris Fuller
Christopher Nortje
Chris Mountford
Dariusz Kordonski
David Tang
Eduardo Soares
Edward Zhang
Eric Dalgliesh
Filip Rogaczewski
Gilmore Davidson
Graham Carrick
Grzegorz Tańczyk
Ian Dick
Ian Grunert
Ignat Alexeyenko
Ivo Bosticky
Jaiden Ashmore
Jaime Sanchez
James Hatherly
James Hazelwood
James Winters
Jason Sheehy
Jeroen De Raedt
Jeshua Morrissey
Jimmy Kurniawan
Jonathan Raoult
Jonathon Creenaune
Joshua Ali
Julius Hocman
Kayne Barclay
Krystian Brazulewicz
Luis Miranda
Lukasz Wlodarczyk
Łukasz Pater
Maciej Nowakowski
Maciej Opala
Marcin Gardias
Markus Kramer
Martin Meinhold
Matt Harrison
Michael Elias
Michael Tokar
Michal Orzechowski
Mike Sharp
Miroslav Stencel
Nikolay Petrov
Norman Atashbar
Oliver Wessels
Oswaldo Hernandez
Patrick Teen
Pawel Bugalski
Pawel Niewiadomski
Pawel Skierczynski
Przemek Borkowski
Richard Cordova
Robert Smart
Roman Tekhov
Sean Curtis
Sergio Cinos
Stanislav Dvorscak
Sunny Kalsi
Symphony Wong
Trevor Campbell
Wojciech Urbanski
Zehua Liu

Sydney Support

Bejoy Jaison
Chung Park Chan
Daniel Watania 
David Currie
David Mason
Matthew Hunter
Mauro Badii
Melissa Klingler
Michael Andreacchio
Nick Mason
Paul Greig

Amsterdam Support
Alex Conde
Bastiaan Jansen
Dora Wierzbicka
Ivan Maduro
Mick Nassette
Miranda Rawson
Peter Koczan
Ruchi Tandon
Shannon Mackie
Theodore Tzidamis
Yilin Mo

Brazil Support
Andre Quadros Petry
Benito Picarelli
Bruno Rosa
Clarissa Gauterio
Danilo Conrad
Eric Kieling
Felipe Willig
Jorge Dias
Lucas Lima
Luciano Fagundes
Marcus Silveira
Matheus Fernandes
Ricardo Carracedo
Pedro Cora
Pedro Souza
Pietro Schaff
Tiago Kolling Comasseto

Kuala Lumpur Support
Ahmad Danial
Ahmad Faisal
Ala Al-Shargabi
Anna Monica Cardino
Azwandi Mohd Aris
Daryl Chuah
Daniel Leng
Immanuel Siagian
Janet Albion
Joe Wai Tye
John Chin Kim Loong
Julian Rahmadiputra
Kumar Ramajillu
Muhammad Fahd
Razaq Omar
Richie Gee
Taiwo Akindele
Vicky Kharisma
Viet Dung Nguyen
Voon Kiat Gan
Yew Teck En
Zulfadli Noor Sazali

San Francisco Support
Boris Berenberg
David Chan
David Maye
David Nicholson
Earl McCutcheon
Gary Sackett
Ivan Tse
James Giles
Jason Worley
Jeff Curry
John Garcia
Jordan Robison
Justin Burke
Kyler Johnson
Mary Avalos
Michael Thai
Osman Afridi
Pelle Kirkeby
Rick Bal
Thomas Garske
Tim Evans
Turner Benard

General Manager

Bryan J. Rollins 

Product Management
Anu Bharadwaj
Bartek Gatz
Iwona Stankiewicz
Jason Wong
Josh Devenny
Martin Jopson
Megan Cook
Roy Krishna 
Tom Kotecki

Product Marketing Management
Caroline Nyce
Dan Radigan
Jake Brereton
Aileen Horgan
Angela Blair
Ken Olofsen

Program Manager
Simone Houghton 

Head of Development
Paul Slade 

Development Management
Graham Carrick
Martin Henderson
Nick Menere
Tomasz Ulicki
Wojciech Seliga

Becc Roach

Benjamin Humphrey
Dean Hudson
Jay Rogers
Krzysztof Piwowar
Ross Chaldecott 

Quality Assistance  
Kiran Shekhar
Michal Kujalowicz
Penny Wyatt
Peter Obara
Sergio Cia
Sripathi Pai

Technical Writing  
Andrew Lui
Christine Burwinkle
Paul Watson
Warren Thompson

Service Enablement 
Chris Le Petit
Patrick Hill

Mark Lassau
Matt Quail
Slawek Ginter


  • No labels


  1. Link to "JIRA 6.3 Upgrade Notes" points to upgrade notes for v6.2.

    1. Hey Mark, sorry I can't seem to replicate that. If you didn't come across them, they're located here: JIRA 6.3 Upgrade Notes

      Cheers, Christine

      1. It is fixed now in version 25 of the page...  but was broken in version 24.

        1. By default the main page link takes you to JIRA 6.2 - I tried this 2 times today

  2. System tab in a new "User-created assets" section

    is in reality

    System tab in a new "SHARED ITEMS" section

  3. Looks like all workflows changed OPEN to Triage. Wonder what else changed from 6.1.X to 6.3.1

    1. Hi Alan,

      Yes, we changed the workflow patterns in JIRA 6.2, you can read up on the changes in the release notes. There were also a few other changes that may be of interest to you. You could also take a quick snapshot view of our changes from JIRA 6.1 to JIRA 6.3 by reviewing the release summary.

      Hope this helps,


  4. Just a minor thing, the release date (for 6.3) is missing on this page.

  5. Hi the JIRA team,

    Just wondering why the release notes do not contain bug fixes? I appreciate the new features but for me I am also interested in the list of bugs fixed. 




  6. 6.3.6 released and no release notes?

    1. Hi Davet,

      You should be able to find them here: JIRA 6.3.6 Release Notes. If not, please let me know!



  7. Thanks Warren - much appreciated

    In the good old days there used to be a direct link to release notes on the JIRA download page - just like the one they still have on the Confluence download page.



  8. Hi,

    1.We are running Atlassian JIRA v5.0.3 on Windows Server 2012 R2, we want to upgrade to the latest (6.3.6).  Not sure whether to upgrade directly or if we should upgrade to 5.2 then 6.0 then 6.3.x, for instance. 

    2.If the upgrade process fails, is there a way to return, downgrade 6.3.x to version 5.0.3? 


  9. I'm puzzled by the "inline ticket creation" thing.  On my system, using Scrum, when I go to create a ticket using that button, I get the full dialog.  There is an info box at the top saying that that is because of the way my board is configured. Yet I have found nothing so far to indicate what that might be.  The JIRA 6.4 EAP documentation ( shows the full dialog, mentions inline adding nowhere else.  The release notes for JIRA 6.3 (this page) isn't helping.  A little help?

    1. Hi Jeff Grimmett,

      The inline issue create works by automatically adding the issue to the project your board is linked to. If your board covers more than one project, then inline issue create doesn't know what project to put the issue in, and therefore what workflow to use. It then prompts you to use the full create issue dialog box so you can select the project, which in turn applies the correct workflow.

      Hope this helps!



      1. Warren,

        That explains it perfectly. The board I was testing it with was linked to two different projects.


  10. Hi Robert Hall

    I have the same question.
    I have the JIRA version 5.2.10 and I would like to migrate to version 6.3.
    What is your experience? Can you migrate directly to 6.3 from 5.0?