JIRA 5.2 Release Notes

• 新しいシステム フィルター — JIRA で最も一般的なビュー（「自分がオープンした課題」、「自分が報告」、「最近の表示履歴」、「すべての課題」）を簡単にフィルターできます。
• Favourite filters on the navigator — Quickly switch between views. Your favourite filters are now just a click away.
• Intuitive filter management — See who owns a filter at a glance and whether changes have been made.
• 新しい検索バー — 検索で希望の条件を選択するだけです。目的の検索条件に焦点を当て、他の部分は非表示にします。
• Ad-hoc searches — Search and refine on-the-fly with immediate results. Refresh your results without reloading your page.
• 複雑な検索— 複雑な検索を簡単に作成して実行できます。新しい検索 UI によって、プロジェクトの数、カスタム フィールド、または JIRA の構成にかかわらず、検索がシンプルになります。

Read the documentation...

Background re-index — JIRA now has the option of re-indexing issues in the background. Performing a background re-index allows your users to use JIRA as normal. You won't need to schedule system-wide downtime just to perform a re-index.

Performance improvements — This release includes a multitude of performance improvements. You may not notice every tweak we've made, but it all adds up to a better user experience.

_{Faster loading of the View Issue page — Smarter loading of attachment thumbnails and the speed to render wiki markup has been increased.
Issue search — Faster results for searching (up to four times faster) when a project has an extremely large number of issue type or custom fields.
Searching with large "NOT IN" clauses — Searches with clauses like "fixVersion not in releasedVersions()" are now at least ten times faster, depending on the data size.
Other areas of increased performance — GreenHopper queries that use nested filters, managing project versions with an extremely large list (all browsers except Internet Explorer), and calculating the assignee field when performing large bulk edits. 
Indexing — More low level Lucene options exposed so you can tune Lucene to perform better in your specific environment.
Smarter use of memory — Reduction in the memory required to interpret Velocity files, resulting in faster page loads.
Faster exports — XML exports with Postgres and MySQL are no longer put into memory. They are now done in batches which allows JIRA to back up extremely large instances.
Faster imports — The garbage collection profile has been improved, resulting in less memory churn and a better performing import process.
Notification table — This table is no longer used and will automatically be deleted, resulting faster backups and imports as there is less data to migrate.}

Reduced Memory Usage

^{More efficient Search Index caching — Memory usage of searches has improved tenfold. This is particularly noticeable on very large instances that are very busy.
Removed the massive memory use of Postgres and MySQL in data export — You no longer need to increase memory size to very large amount to get an export to work.
Smarter pooling of UI rendering resources — This change saves 90MB of memory.}

SSL configuration via the JIRA configuration tool — If you want to run JIRA over SSL or HTTPS, you won't need to tinker around in XML files anymore. The JIRA configuration tool has a new screen that lets you easily configure access via HTTPS. The configuration tool also validates your configuration, so you won't need to worry if you've mistakenly entered an invalid certificate. Read the documentation...

Improved JIRA Data Generator — In JIRA 5.1, we built the JIRA Data Generator as part of our Enterprise performance work. This tool helps customers create large JIRA data sets quickly, which is useful for testing how your instance will perform at a projected rate. We also released a set of performance test scripts that can be used to test against data sets created by the JIRA Data Generator.  In this release, we've improved the JIRA Data Generator to support screen schemes and field configurations. The tool is not bundled with JIRA, but it is free and customers can get it from the Atlassian Marketplace: JIRA Data Generator.

HTTP Request Log Analyser — The new JIRA HTTP Request Log Analyser provides an analysis of the traffic on your JIRA instance, such as the maximum requests per minute, that can help you performance-tune your JIRA instance. We originally developed this tool to help our customers provide us with performance data for their JIRA instances. This tool is not bundled with JIRA, but it is available as a free download. We also have a summary of the results from our JIRA instances and from some anonymous customers.

New guides — Federating JIRA - Managing Multiple Instances and Scaling JIRA Agile.

Enterprise resources — If you haven't browsed our enterprise resources before, you can find them here: Enterprise Resources. You'll find guides on scaling JIRA, establishing staging server environments for JIRA, garbage collection tuning, and more.

Custom field performance — In JIRA 5.1, we gave our Enterprise customers the Scaling JIRA guide which explains how customers can get the most out of JIRA in large deployments. This guide describes how there are many factors that affect JIRA performance, besides the total number of issues. One of these factors is custom fields. In this release, we've investigated how the configuration of custom fields can affect performance. You can view our findings in the updated Scaling JIRA guide.

Simply register a webhook in JIRA with the URL where the callback should be sent. Any time any issue changes in JIRA, a JSON notification will be sent to the URL.

You can also refine webhooks to suit your needs:

• Constrain a webhook to fire for a set of issues and/or specific issue events.
• Use a variable to include the key of the issue that fired it.
• Configure a workflow post-function to fire a webhook.

Following on from the improvements to workflow administration in JIRA 4.4 and project administration in JIRA 5.1, we're continuing to make editing workflows easier within your project. You'll still have the power and flexibility of JIRA workflows at your fingertips, but configuration is much more intuitive.

Project workflows are now shown as a visual representation —  a diagram of each project workflow is displayed in a table, with the associated issue types alongside. The old text-based view of each workflow is still available as well, if you prefer.

Configuring project workflows is also much easier. Want to preview changes as a draft before publishing? Want to browse through diagrams of the workflows in the system when adding a workflow? Want to assign multiple issue types to a workflow in a single step? You can now do all of these tasks and more.

Read the documentation...

The screen designer has been overhauled in this release. Screens are as customisable as ever, however the user interface is faster and much simpler to use. You won't have to wrestle with controls when reordering — just drag and drop to move a field or tab. Autocomplete is now used when adding fields, making this process quicker and easier as well.

Read the documentation...

プロジェクトのための合理化されたユーザー インターフェース

We've been working hard to improve the user interface when you are browsing a project, so that you can concentrate on the task at hand without any distractions. The list of improvements are in the table below:

UI 機能	注意	新しい UI のスクリーンショット
New Create New Project button on the Browse Projects > All Projects page	N/A
Browse Project > Summary tab redesigned: プロジェクトの参照ページで利用可能になったプロジェクトの管理ボタン Activity Stream only shows activity on JIRA issues and JIRA plugins 課題： 最近更新セクションが削除されました  課題：未解決セクションが削除されました Versions: Unreleased section moved to different position on tab Show/hide toggle for additional versions removed "Eyeball" toggle replaced with smart switcher at bottom of list	Administer Project button used to be on Browse Project > Summary tab (now removed) Issues: Updated recently and Issue: Unresolved sections superseded by Activity Stream.
プロジェクトの参照 > 課題ページで直接利用可能な標準課題フィルタ	Used to be in Filters dropdown on Browse Project > Summary tab (now removed)
バージョンの参照 > 課題ページで直接利用可能な標準課題フィルタ	Used to be in Filters dropdown on Browse Version > Summary tab (now removed)
コンポーネントの参照 > 課題ページで直接利用可能な標準課題フィルタ	Used to be in Filters dropdown on Browse Component > Summary tab (now removed)
プロジェクト概要およびページのユーザー セクションがロールという名前に変更されました	N/A
プロジェクト > 人気の課題ページが再設計されました	N/A
プロジェクト > ラベル ページが再設計されました	N/A

Jira 管理ヘルパー

We've bundled the popular JIRA admin helper plugin in this release. This tool helps JIRA administrators to diagnose and fix any of the following problems:

課題コレクターのコピーと編集

JIRA 5.1 では、JIRA 課題コレクターが導入されました。これによって、JIRA インスタンスに課題を作成する web サイトに JIRA フィードバック フォームを埋め込むことができます。このリリースでは、課題コレクターの編集とコピーの機能が追加されました。既存の課題コレクターを微調整したり、完全な新しいものの基礎として使用したりしています。

Read the documentation...

より高速で信頼性の高いメンション

JIRA 5.0 ではメンションが追加されました。これによって JIRA ユーザーは簡単に、メールで他のユーザーと課題を共有できるようになりました。このリリースでは、この機能に対して重大なパフォーマンスの改善を導入しました。「@」の後に文字を打つと、ユーザー名がより素早く提案されることに気付くと思います。また、提案される結果はより正確で信頼性が高くなっています。

Compatibility with Confluence Workbox Notifications

JIRA 5.2 is compatible with Confluence Workbox Notifications (introduced in Confluence 4.3). Read more in the Confluence 4.3 release notes.

Platform changes

We have made a number of platform changes in this release, including upgrading JIRA to run on Tomcat 7 and support for Java 7. Some of these changes affect the installation and upgrade process for JIRA. 

Please read the upgrade guide for details.