JIRA 6.2 Release Notes

Visualize development

Unify issues and source like never before

In JIRA 6.1, we started the journey towards seamless integration with your coding tools. We're continuing this in JIRA 6.2, by providing more code-related information in your issues, that you can assess and action. Create a branch, see commits and pull requests, watch builds, and more!

This release also includes an improved workflow designer, simpler issue type configuration, new status lozenges, auditing, and more!

JIRA 6.2 Upgrade Notes

25 February 2014

New code integration features for issues

The new Development panel, which is shown on every issue, helps you to evaluate the development status of an issue at a glance. If you need to investigate further, click any item to display more details, or drill down into the development tool.

Connect to one of these compatible applications to enable the following:

  • Bitbucket or Stash: view and create branches, view commits, view and create pull requests
  • FishEye/Crucible (Git/Subversion/Perforce/CVS): view branches, view commits, view and create reviews
  • Bamboo: view the status of builds and deployments
  • GitHub/GitHub Enterprise: view branches, view commits, view and create pull requests

Learn more: Integrating with a development tool and Using the Development panel

Enhanced workflow designer

The workflow designer is faster and easier to use in this release. We've added a range of new features and made the user interface cleaner and less cluttered. You can now click to create transitions, reuse existing transitions, zoom (with the 'alt' key or the +/- controls), drag and drop to retarget the destination of a transition, and more!

In fact, the workflow designer can do everything that we supported in the old 'classic' workflow designer, so we've given the 'classic' designer a well earned retirement and removed it from JIRA.

Learn more...

Simple issue type configuration

We've simplified issue type configuration in this release. Don't hunt around in JIRA administration to find the workflow or screen for an issue type. The issue types associated with a project are now tabs on the project's administration screen.

This approach makes it easier to understand how your projects are set up. Each tab also provides access to the workflow designer and screen designer (JIRA administrators only), so you can configure an issue type without leaving the project.

Learn more...

New status lozenges

This release introduces new "lozenges" to represent statuses in JIRA. We've switched from the old icon+text representation to make it easier for users to locate and identify statuses. The new status lozenges also conform to the Atlassian Design Guidelines (ADG). This blog post explains the background behind this change.

We no longer support custom images for status icons. However, you will be able to configure statuses to use any one of the slick new status colors (categories) in JIRA. 

Learn more...


JIRA now tracks and records a range of configuration changes in an audit log. This can help you diagnose problems in JIRA or can be used for security purposes. Find out when a user was added or removed, when a workflow scheme was modified, and more. Note, auditing is disabled by default — you will need to enable it to start tracking changes in JIRA.

This is the initial release of auditing. We're still working on a number of improvements that you'll see in future JIRA releases.

Learn more...

And more!

Of course, there's more! You can read about the other JIRA 6.2 features below. A noteworthy one is that the creator of an issue is now automatically recorded for every issue. This is particularly useful, if you need to know the creator of an issue for compliance reasons. The creator is distinct from the reporter (which can still be configured to be an optional field). On upgrade to this release, JIRA will set the creator to the appropriate reporter in the change history, for existing issues.

The creator can be seen in the issue history. If the creator is the same as the reporter, the name of the creator will be shown in the Reporter field on the issue.

Click to view the other features and improvements in this release:

  Learn more...
  • Back up and recover indexes — Configure JIRA to take snapshots of indexes. Recover an index from a snapshot instead of rebuilding the index, if there is a failure. Learn more...

  • Re-index individual projects — Re-index a single project, rather than re-indexing your entire JIRA instance. Learn more...

  • New 'creator' JQL field — Find issues by their creator by using the new 'creator' JQL field. Learn more...

  • New 'attachments' JQL field Find issues that have attachments or issues that do not have attachments with the new 'attachments' JQL field. Just add the clause "attachments IS EMPTY" or "attachments IS NOT EMPTY" to your advanced search query. Learn more...

  • Filtering for User Picker custom field  — You can now limit the users that can be selected in a user picker custom field, to specified groups and/or project roles. Just configure your user picker custom field and choose the new Edit User Filtering link. Learn more...

  • Inline editing can now be disabled — Inline editing, i.e. clicking to edit a field, can now be disabled for your JIRA site in the General Configuration options. It is still enabled by default.

  • Internet Explorer 11 is now supported

The JIRA 6.2 team


Adam Jakubowski
Aleksander Mierzwicki
Andreas Knecht
Andrew Swan
Antoine Büsch
Arkadiusz Głowacki
Ben Sayers
Ben Wong
Bradley Ayers
Brenden Bain
Brydie McCoy
Charles O'Farrell
Chris Darroch
Chris Doble
Chris Fuller
Chris Mountford
David Tang
Edward Zhang
Eric Dalgliesh
Filip Rogaczewski
Gilmore Davidson

Graham Carrick
Grzegorz Tańczyk
Ian Grunert
Ignat Alexeyenko
Jaiden Ashmore
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 Henderson
Martin Jopson
Martin Meinhold
Michael Elias
Michael Tokar
Michal Orzechowski
Mike Sharp
Miroslav Stencel
Nick Menere
Nikolay Petrov
Oliver Wessels
Oswaldo Hernandez
Patrick Teen
Pawel Bugalski
Pawel Niewiadomski
Pawel Skierczynski
Pierre-Etienne Poirot
Przemek Borkowski
Robert Smart
Roman Tekhov
Sean Curtis
Sergio Cinos
Stanislav Dvorscak
Sunny Kalsi
Trevor Campbell
Wojciech Urbanski
Zehua Liu


Mark Lassau
Matt Quail
Slawek Ginter


Sydney support
Bejoy Jaison
David Currie
David Mason
Matthew Hunter
Mauro Badii
Michael Andreacchio
Michael Knight
Nick Mason
Paul Greig

Amsterdam support
Alex Conde
Bastiaan Jansen
Dora Wierzbicka
Ivan Maduro
John Inder
Mick Nassette
Miranda Rawson
Peter Koczan
Ruchi Tandon
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

Abdoulaye Kindy Diallo
Ahmad Danial
Ahmad Faisal
Ala Al-Shargabi
Amanda Wei Sai Nan Wei
Azwandi Mohd Aris
Chung Park Chan
Daryl Chuah
Daniel Leng
Daniel Watania
Immanuel Siagian
Janet Albion
Joe Wai Tye
John Chin Kim Loong
Kumar Ramajillu
Muhammad Fahd
Razaq Omar
Richie Gee
Steven Trung Tran
Vicky Kharisma
Voon Kiat Gan
Yew Teck En
Zulfadli Noor Sazali

San Francisco support
Boris Berenberg
David Chan
David Maye
David Nicholson
Gary Sackett
Ivan Tse
Jason Worley
Jeff Curry
John Garcia
Mary Avalos
Osman Afridi
Pelle Kirkeby
Rick Bal
Turner Benard

Service Enablement
Chris Le Petit
Patrick Hill


Product management
Anu Bharadwaj
Bartek Gatz
Iwona Stankiewicz
Josh Devenny
Megan Cook
Nick Strybosch
Roy Krishna 
Tom Kotecki

Product marketing management
Caroline Nyce
Dan Chuparkoff
Dan Radigan
Jake Brereton

Program manager
Simone Houghton 

Development manager
Paul Slade
Wojciech Seliga

General manager
Bryan J. Rollins

Cross-product team

Becc Roach

Benjamin Humphrey
Jay Rogers
Krzysztof Piwowar
Ross Chaldecott 

Quality assistance  
Kiran Shekhar
Michal Kujalowicz
Penny Wyatt
Peter Obara
Veenu Bharara
Sergio Cia

Technical writing  
Andrew Lui
Paul Watson

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

15 Archived comments

  1. User avatar

    Jason Smith

    "We're continuing this in JIRA 6.2, by providing more code-related information in your issues, that you can assess and action.":

    "action" doesn't fit grammatically in that sentence

    25 Feb 2014
    1. User avatar


      In business speak, nouns can be verbs and verbs can be nouns.  Ever heard the phrase "I have a big ask for you."? Yeah, it bothers me too.

      05 Mar 2014
  2. User avatar

    Antony Galdi

    We are writing to inform you of a critical security vulnerability that affects all downloaded versions of JIRA up to and including 6.1.3, Confluence up to and including 5.4.1

    Where is the detail on what the security vulnerability is? There's no mention of that here or elsewhere.

    26 Feb 2014
    1. User avatar

      Eric Kieling [Atlassian]

      Here you can find more details: JIRA Security Advisory 2014-02-26

      26 Feb 2014
  3. User avatar


    6.1.x was a disaster. Each released introduced many bugs and performance issues, some that had been previously fixed in the 5.x releases.  Hoping 6.2.x is more stable and reliable.

    27 Feb 2014
  4. User avatar

    Ingo-Stefan Schilling

    I still miss a fix for the JAVA_HOME - JRE_HOME issue that I mentioned in Re: JIRA 6.1.7 Release Notes.

    Even though my work-around does still work, that is no option!

    I would like to stress this again, if one is using SSL (which everyone should), he/she either will have to import the certificate to each JRE environment - in the worst case this means to all atlassian product installations that rely either on Crowd directly (as in our scenario) or Jira-Crowd. However, this is for large environments inacceptable - also maintainability of Java isn't really given if half-douzend JREs have to be maintained. 

    05 Mar 2014
    1. User avatar

      Andrew Lui [Atlassian Technical Writer]

      Hi Ingo-Stefan,

      I talked to our support team. Can I ask you to raise a support request, so that they can figure out the best way to progress your issue?

      Kind regards,

      05 Mar 2014
  5. User avatar

    Laszlo Kremer

    Wow, project reindex sounds promising!

    18 Mar 2014
  6. User avatar


    We have some custom stored procedures that broke during our last upgrade. The "Pkey" field is no longer populated in the JiraIssue table. Since this is the primary means of identifying issues in our external reporting system, is there a way to configure 6.2 to maintain and populate this field as in previous versions?

    21 Mar 2014
    1. User avatar

      Leon Wright

      The data is still there, the issue numbers have been separated from the project key to allow project keys to be renamed. I can't recall exactly what columns, but it won't take you long to find.

      24 Jun 2014
  7. User avatar


    What issues were fixed in this release?

    Is this the correct filter?  96 issues

    26 Mar 2014
  8. User avatar


    Where can I find the md5 sum of the new release

    Looked here: https://www.atlassian.com/software/jira/download (no md5)

    And here too: https://www.atlassian.com/software/jira/download-archives (no 6.2.2)


    07 Apr 2014
  9. User avatar

    Adolfo Casari

    Simple issue type configuration

    ..... This approach makes it easier to understand how your projects are set up. Each tab also provides access to the workflow designer  and screen designer, so you can configure an issue type without leaving the project.


    The above means that a Project Administrator can alter workflows and screens?

    11 Jul 2014
  10. User avatar

    Topaz Gino


    We intend to upgrade JIRA to version 6.x. Is the "HiQo Confluence Links" for JIRA plugin available in this version? Would it work with JIRA 6.x? Also - how does Confluence integrate with JIRA on JIRA 6.x release? 



    17 Dec 2014
Powered by Confluence and Scroll Viewport