Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

Accelerate change

Help your team embrace change with JIRA 6.1

JIRA 6.1 picks up where JIRA 6.0 left off, introducing more improvements that help you get work done faster. Features like the new workflow designer and intuitive custom field configuration, let you introduce change to your team without slowing them down.

We are also starting a new journey towards seamless JIRA integration with your coding tools. The new create branch functionality in JIRA 6.1 is the first improvement, with many more to come.

   
JIRA 6.1 Upgrade Notes

24 September 2013

New workflow designer

The new workflow designer is fast, modern and easy to use. Built using HTML5, the latest HTML standard, it loads instantly and is incredibly responsive. On top of this, we've added features to help JIRA administrators build workflows more easily — design in full screen mode, snap lines to statuses (geometric snap lines), select a status to highlight transitions, and more.

Users also benefit from this feature: when viewing an issue, click View Workflow (next to the Status field) to show an accurate view of the workflow designer (one of our highest voted feature requests).

Learn more...

 

 




New project templates

JIRA 6.1 continues our work from previous releases to get you started faster. You can now choose from two new templates when creating a new project in JIRA. Get up and running quickly with the Simple Issue Tracking project, which has a simple three-step workflow that is easy to understand; or choose the Software Development project, which is configured to reflect a basic development and review process.

Learn more: Simple Issue Tracking Project and Software Development Project

Intuitive custom field configuration

We've made it easier to create custom fields and put them where you want. Viewing an issue and think that it needs a new field? Simply click Admin > Add field to choose an existing custom field or create a new one. The field is also added to the Create and Edit screens, so you can use it straight away.

Field types are now categorized into Standard and Advanced when creating a custom field. Standard types also offer a preview of the field, so you can see what you are creating in advance.

Learn more...




Enterprise enhancements

Edit project key

One of the most voted for feature requests has been implemented in this release: the ability to edit a project key. It's simple but powerful — just change a single field to edit the key for an existing project. JIRA will automatically update related data across all of your projects.

Learn more...

Change usernames in LDAP

JIRA now supports changing usernames when connected to an external LDAP user directory. This means that JIRA treats name changes in LDAP as renames, rather than deleting and adding a user (which did not work). For most LDAP implementations, this will work out of the box. In a small minority of cases, further configuration is required.

JIRA password policy

The JIRA password policy feature enables JIRA Administrators to set limits and restrictions on the types of passwords their users can create.

Learn more...

 

More integration with your coding tools

You've always been able to link commits from Bitbucket and Stash to JIRA issues, making it easy to understand which issues are fixed and the code changes involved. However, we're adding new features to expand the ways you can manage commits, builds, and deployments within the context of your planning resources in JIRA.

In this first release of these improvements, if you use Bitbucket or Stash to manage your code repositories, you'll be able to create code branches directly from issues in JIRA or JIRA Agile. The new Create branch link will open your connected repository application and launch the process of creating a branch for you. If you have multiple applications connected, then you can choose where you'd like to create the branch.

(warning) Note, the ability to create branches from JIRA in Stash requires Stash 2.8, which.will be released next week on 1 October 2013 (watch this page for updates). You can create branches from JIRA in Bitbucket now.

And more!

We're not stopping here! You will find plenty more 6.1 features listed below. The most notable of these are the name changes for JIRA add-ons: GreenHopper has been renamed to JIRA Agile and Bonfire has been renamed to JIRA Capture. This is part of a move to align these two add-ons more closely with JIRA. You will see associated user interface changes in JIRA in this release. Please be assured that your existing licenses and support entitlements are unchanged. This is a change of product name only. Read this blog post for more information.

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

 Learn more...
  • Easier issue navigator column configuration —  Show exactly what you need when triaging issues. In this release, you can easily change the columns for search results displayed in List View. Simply click Columns (top right) to choose the desired columns, then drag and drop them where you want.

     Show me...

  • Improvements to workflow text mode — In line with the updated workflow designer, we have also updated many of the pages in text mode. Specifically, the page that allows you to view a particular status or transition, as well as its post function, conditions and validators.
  • New default workflow and assignee — We've made two changes to simplify the out-of-box experience for new projects in JIRA. First, the default workflow no longer requires a user to be the assignee to transition an issue from one status to another. Second, the default for Allow Unassigned Issues is now set to ON (for new instances only) and the Default Assignee is now set to 'Unassigned' when you create a new project. Together, these changes allow issues to be worked on by anyone, rather than have one person be the bottleneck.

     Please note...

    Default workflow: If you prefer the old default workflow behavior, you can change your workflow or import the Classic Default JIRA Workflow.
    Allow Unassigned Issues: Existing instances keep the current default (Allow Unassigned Issues is set to OFF).

  • JIRA Redmine Importer now available — We've added a JIRA Redmine Importer plugin that enables you to import data from Redmine directly into your local JIRA site. Learn more...
  • New look for email notifications — Email templates for JIRA have been improved to reflect the Atlassian Design Guidelines look and feel. Learn more...
  • New whitelist for JIRA — JIRA's whitelist is now more intuitive and easier to configure. Learn more...
  • Faster access to JIRA reports — You can now access JIRA reports directly from its own tab under the Browse Project page.

The JIRA 6.1 team

Development

Adam Jakubowski
Aleksander Mierzwicki
Andreas Knecht
Andrew Swan
Antoine Büsch
Anund McKague
Ben Wong
Bradley Ayers
Brenden Bain
Chris Darroch
Chris Doble
Chris Fuller
Chris Mountford
David Tang
Edward Zhang
Eric Dalgliesh
Filip Rogaczewski
Gilmore Davidson
Ian Grunert
Ignat Alexeyenko
Jaiden Ashmore
James Hatherly
James Hazelwood
James Winters
Jeroen De Raedt
Jeshua Morrissey
Jimmy Kurniawan
Joanne Cranford
Jonathan Raoult
Jonathon Creenaune
Joshua Ali
Joshua Hansen
Justus Pendleton
Kayne Barclay
Luis Miranda
Lukasz Wlodarczyk
Maciej Nowakowski
Maciej Opala
Mark Lassau
Markus Kramer
Martin Henderson
Martin Jopson
Martin Meinhold
Michael Elias
Michael Ruflin
Michael Tokar
Michal Orzechowski
Mike Sharp
Nick Menere
Nikolay Petrov
Oswaldo Hernandez
Pawel Bugalski
Pawel Niewiadomski
Pawel Skierczynski
Pierre-Etienne Poirot
Przemek Borkowski
Robert Smart
Roman Tekhov
Scott Harwood
Sean Curtis
Sergio Cinos
Trevor Campbell
Wojciech Seliga
Wojciech Urbanski
Zehua Liu

Architecture

Brad Baker
Matt Quail
Slawek Ginter

Support

Sydney support
Christopher Shim
David Currie
David Mason
Matthew Hunter
Mauro Badii
Michael Andreacchio
Michael Knight
Nick Mason
Paul Greig
Renjith Pillai

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
Bruno Rosa
Clarissa Gauterio
Eric Kieling
Felipe Willig
Jeison Spaniol
Jorge Dias
Lucas Timm
Lucas Lima
Marcus Silveira
Marlon Aguiar
Matheus Fernandes
Ricardo Carracedo
Pedro Cora
Pedro Jardim
Pietro Schaf
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
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

Management

Product management
Bartek Gatz
Bryan Rollins
Carine Ma
Edwin Wong
Josh Devenny
Megan Cook
Roy Krishna 
Shihab Hamid
Tom Kotecki

Product marketing management
Caroline Nyce
Dan Chuparkoff
Dan Radigan

Program Manager
Simone Houghton 

Development manager
Paul Slade

Cross-product team

Design
Becc Roach

Benjamin Humphrey
Jay Rogers
Judd Garratt
Krzysztof Piwowar
Ross Chaldecott 

Quality assistance  
Kiran Shekhar
Michal Kujalowicz
Panna Cherukuri
Penny Wyatt
Peter Obara
 
Veenu Bharara

Technical writing  
Andrew Lui
Rosie Jameson
Susan Griffin

  • No labels

17 Comments

  1. Looking good! Please would someone update the add-ons so that things like Agile can be installed, thanks.

    1. Thanks Matt! The add-on references have been updated for JIRA Agile and JIRA Capture. The other add-ons should be sorted soon.

  2. It would be nice to see some GitHub support for the Development Tools, any chance of that coming in the near future?

    1. Hi Hunter, what are you looking for in particular? You can currently see your commit information on your JIRA issues using the DVCS Connector.

      1. Hey Megan, I was talking about the ability to create Feature branches and such. This update allows Bitbucket, Stash and a few others to create feature branches from issues, but Github is left out on the fun.

        1. Ah ok, thanks Hunter. At this stage there are no plans to add creating a branch for Github. This doesn't mean that they will be left out for all future updates to Development Tools support though. 

          1. Alright, thanks for the update. Fingers crossed it does get implemented, or the plugin adds the functionality.

  3. Anonymous

    Hi, is there a way to view Epics in line on the Plan board – in priority order – along with their User Stories? 

     

    Thanks,

    Carla 

    1. Hi Carla,

      You can indeed see Epics in the Epic panel on the left. We treat them as separate entities that are used to group User Stories, which is why we don't display them along together.

      You could in theory create a User Story (or an issue of a custom type) with a big estimate, which you then convert to an actual Epic as you break it down, but I'm not sure if this overhead is worth the effort.

      Tom Kotecki

      Product Manager, JIRA Agile

      1. Anonymous

        Thank you, Tom. Is there a way to have the Epics show up within a designated sprint in "Plan" view? 

         

        1. No - that would imply you complete an entire set of Epics in a single sprint (which is highly unlikely). Each story has an Epic label displayed next to it though, does that not do the trick for you?

          Tom

          1. Anonymous

            For my view, the epic label didn't display next to the respective user stories. In our particular usage, many of our epics can be completed within the duration of a single sprint, so it was helpful to be able to have a comprehensive the epic and user stories. 

            1. Anonymous

              *comprehensive view of the epic and user stories. (smile)

  4. Whoah! The new workflow designer is a huuuge relief! Thank you for that, it is a pleasure to work with, and users like to read it. Awesome! Cool! Congratulations!

  5. Is the "New Work Flow Designer" backward compatible with workflows created in previous versions?

    1. Hi Violette,

      The new workflow designer does work with the workflows you have created in previous versions. It will place your statuses in the same place as they currently are, and make a best attempt to place your existing transitions.

      Josh

  6. I have upgraded my test instance to JIRA 6.1.7 which now causing me exceptions while using workflow designer.

    Problems are similar to the once explained in Re: Exceptions occur in Workflow Designer / View Workflow using Java 1.7

     

    I am using 

    java version "1.7.0_05-icedtea"
    OpenJDK Runtime Environment (rhel-2.2.1.el6_3-x86_64)
    OpenJDK 64-Bit Server VM (build 23.0-b21, mixed mode)

    Do I have to downgrade my java version in order to make workflow designer work ?

     

    Thanks,

    Sumit