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

Atlassian Software Systems is delighted to present JIRA 3.11.

Upgrading to JIRA 3.11 is free for all customers with activeJIRA software maintenance as at 24th September 2007.This release focuses on time-tracking. Time-tracking data (that is, the estimated and actual time spent on an issue) now includes the issue's sub-tasks. The aggregated time-tracking data is displayed both within individual 'parent' issues and in the Issue Navigator, so it can be easily reported on, exported to Excel, etc.
Being able to track your project's Road Map (scheduled issues) has long been a useful feature of JIRA. But how do you manage programs of multiple, related projects? In JIRA 3.11, the new Road Map portlet shows upcoming milestones across multiple projects of your choice.




Upgrading to JIRA 3.11

JIRA 3.11 can be downloaded from the JIRA Download Center. Before upgrading, please refer to the JIRA 3.11 Upgrade Guide.

 

Thank you for your feedback:

31 new feature and improvement requests implemented
223 votes fulfilled

Your votes and issues help us keep improving our products, and are much appreciated.
 
Highlights of JIRA 3.11:

Highlights of JIRA 3.11:

Sub-task progress shown within issues

When viewing an issue, you can now choose whether to view time tracking data for the issue only, or for the issue plus its sub-tasks:

  • Click 'Issue' (in the Time Tracking box) to show time tracking data for the 'parent' issue only, or 'Issue & Sub-Tasks' to include the issue's sub-tasks.
  • Time tracking data comprises:
    • Original Estimate (blue) — the amount of time the issue was expected to take to resolve, when it was first created.
    • Remaining Estimate (orange) — the remaining amount of time the issue is currently expected to take to resolve.
    • Time Spent (green) — the amount of time logged working on the issue so far.

Please note that sub-tasks are only available in the Enterprise and Professional editions of JIRA.

Issue Navigator offers sub-task aggregates

To take advantage of the new sub-task aggregates, the following time tracking fields are now available in the Issue Navigator:

  • Progress — an issue's Time Spent, as a percentage of the issue's Original Estimate.
  • Σ Progress — the aggregate time spent on an issue's sub-tasks, as a percentage of the sub-tasks' aggregate Original Estimate.
  • Σ Original Estimate — the aggregate Original Estimate for an issue's sub-tasks.
  • Σ Remaining Estimate — the aggregate Remaining Estimate for an issue's sub-tasks.
  • Σ Time Spent — the aggregate Time Spent for an issue's sub-tasks.

Time Tracking reports now include sub-tasks

  • A 'parent' issue now has two separate sets of time tracking data, if applicable: (1) its own; and (2) an aggregate that includes the issue's own time-tracking plus all sub-tasks that the user has permission to see.
  • The Time Tracking report now includes the aggregate data as shown in the new 'Σ' columns:
  • Additionally, both the Time Tracking report and the Version Workload report now include options for choosing which sub-tasks you would like to include in your reports.

Multi-project 'Road Map' portlet

The new Road Map portlet is a handy addition to your JIRA dashboard. It shows upcoming project milestones (i.e. versions which are due for release within a specified period of time), and a summary of progress made towards completing the issues in those versions.

You can:

Performance improvements

JIRA 3.11 includes some significant performance tuning which should improve the experience of every JIRA user.

  • Page size has been reduced.
  • The effect of GZip compression has been improved due to optimised handling of Javascript and CSS. This will be of benefit to people using Firefox or Internet Explorer 7 browsers.
  • Caching has been optimised (see the Developer Blog).

Indexing improvements

  • 'Bulk operations' now re-index issues one at a time instead of all at once. This allows JIRA to better handle concurrent operations and higher user loads while maintaining index integrity.
  • JIRA now uses Lucene 2.2.0. This has two main benefits:
    • JIRA can now handle the input of and search on dates before January 1st, 1970.
    • JIRA now performs atomic updates to issue and comment indexes, providing greater consistency when searching.

JIRA Labels Plugin

Alongside JIRA 3.11, we're announcing a major overhaul of the JIRA labels plugin. The plugin implements a labels (or tags, sometimes known as folksonomy) custom field for JIRA. Labels or tags make it easier to organise a large set of data by arbitrary, user-defined criteria.

You can read more details on the developer blog.

Plus over 70 other fixes and improvements

Loading
T Key Summary P Status
Bug JRA-14086 Setup page is accessable after JIRA instance has been setup already Blocker Resolved
Improvement JRA-10326 JIRAs HTTP transfers are not efficient - improve web performance Blocker Resolved
Bug JRA-13496 Error message generated in Add Comment Panel when adding comment to an issue Critical Resolved
Bug JRA-13435 Base URL ending in slash breaks filter subscription HTML email links Critical Resolved
Bug JRA-13412 TransitionWorkflow Jelly tag will not work if there is no transition screen Critical Resolved
Bug JRA-13345 Jira RSS 2.0 does not work with standard java parser - pubDate elements are incorrect Critical Resolved
Bug JRA-12948 Incorrectly reporting Installation type as EAR/WAR instead of Standalone when running as a Windows service Critical Resolved
Bug JRA-11877 Automated JIRA backup failes without proper warning Critical Resolved
Bug JRA-10461 Deleting an issue type breaks custom fields that had used it Critical Resolved
Bug JRA-13864 Error is thrown when session timeout expired on editing a comment Major Resolved
Bug JRA-13560 Getting permgen OOME on eac/jira during startup Major Resolved
Bug JRA-13556 setHeader(null) causing NullPointer on Resin Major Resolved
Improvement JRA-13510 An extra warning info for the JIRA standalone installation page. Major Closed
Bug JRA-13502 Sub-task creation fails when browse project permission is give to CurrentAssignee, GroupCF or UserCF Major Resolved
Improvement JRA-13491 Only include calendar javascript and css on pages that require the calendar Major Resolved
Improvement JRA-13490 Ship minified versions of javascript and css files Major Resolved
Improvement JRA-13489 Don't use scriptaculous loader Major Resolved
Improvement JRA-13488 Remove dashboard dependency on scriptaculous Major Resolved
Bug JRA-13443 Subtask quick create submit can submit multiple times with multiple clicks Major Resolved
New Feature JRA-13425 Create Road Map Portlet Major Resolved
Showing 20 out of 77 issues Refresh