JIRA 5.2.11 Release Notes
19 April 2013The Atlassian JIRA team announces the release of JIRA 5.2.11. This point release contains several updates and fixes.
This is the last release in the 5.2.x release cycle.
Upgrading to JIRA 5.2.11 is free to all customers with active JIRA software maintenance.
Don't have JIRA 5.2 yet?
Take a look at all the new features in the JIRA 5.2 Release Notes and see what you are missing out on!
- Viewing an issue's workflow via the View Issue screen now works, even if the name of the workflow has special characters (see JRA-27809 - "View Workflow" link does not work in case when workflow name contains special symbols Resolved ).
Upgrading from a previous version of JIRA
If you are upgrading, please read the JIRA 5.2.11 Upgrade Notes.
Updates and fixes in this release
JIRA 5.2.11 includes the following updates and bug fixes:
|JRA-31948||Upgrade Remote Apps to 0.4.518.6||Mar 05, 2013||May 29, 2015||Eric Dalgliesh||Don Brown [Atlassian]||Closed||Fixed|
|JRA-30113||"People and Dates Section" of Issue View Screen Changed to 2 lines in Chrome after Jira 5.1.1||Oct 15, 2012||Feb 20, 2017||Unassigned||KhongMing KOK [Atlassian]||Resolved||Obsolete|
|JRA-31549||FieldScreenTab configuration not saved consistently to database||Feb 03, 2013||Feb 20, 2017||Roman Tekhov||Vassil Velichkov||Resolved||Fixed|
|JRA-30702||JIRA backup and restore does not handle map data stored by plugins correctly||Nov 26, 2012||Feb 20, 2017||Eric Dalgliesh||Trevor Campbell||Resolved||Fixed|
|JRA-30748||Field names of 'Created Date' and 'Resolution Date' in issue nav are incorrect.||Nov 29, 2012||Feb 20, 2017||Eric Dalgliesh||Kan Ogawa||Resolved||Fixed|
|JRA-32803||URL encoding "View Workflow" link fail when workflow name contains "&" character||Apr 26, 2013||Feb 20, 2017||Unassigned||Philipp Klauser||Resolved||Duplicate|
|JRA-31198||In mention e-mail notification issue link is broken||Jan 09, 2013||Apr 29, 2013||Eric Dalgliesh||Simone Houghton||Resolved||Fixed|
|JRA-27809||"View Workflow" link does not work in case when workflow name contains special symbols||Apr 06, 2012||Feb 20, 2017||Eric Dalgliesh||Andrei||Resolved||Fixed|
Was this helpful?
Thanks for your feedback!