JIRA 6.2 RC 1 Release Notes
2014 年 2 月 10 日
Atlassian is proud to present JIRA 6.2 RC 1. This public development release is part of our Early Access Program (EAP) leading up to the official JIRA 6.2 release. We are making these EAP milestones publicly available so that developers can start assessing the impact of the changes that we are making. Please provide us with your feedback on this release here.
If you are a JIRA developer, please see Preparing for JIRA 6.2 as well as our Java API policy for JIRA.
Read before you install/upgrade: Atlassian does not support upgrades both 'from' and 'to' EAP releases. EAP releases should not be used in production environments as they are not officially supported. For all production use and testing of JIRA, please use the latest official release instead.
We want your feedback!
In this release:
Key Features
新しいステータス バッジ
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. 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 activities in an audit log. Find out when a user was added or removed, or even when a workflow scheme was modified. The audit log doesn't record every single event in JIRA, but it does capture configuration changes that can impact users and projects. This can help you diagnose problems in JIRA or can be used for security purposes.
監査は、デフォルトで無効になっています。Jira で変更の追跡を開始するには、これを有効化する必要があります。
We would love to hear your feedback on this feature. Click the 
button on the audit log to let us know which events you'd like to see supported in future.
シンプルな課題タイプ構成
Issue types associated with the project are now listed on the main project administration page. The issue type tab has also been redesigned, allowing you to access the workflow designer or screen designer for the issue type with a single click.
Improvements to the workflow designer
You can now reuse existing transitions in the workflow designer. Just add a transition and choose the Reuse a transition tab.
You will only be able to reuse transitions that have the same destination status as the new transition you are adding — the values in Transition to reuse field will change depending on the value of the To Status field.
Other features that have been added to the workflow designer include:
- ワークフロー エディターをマウスでスクロールできるようになりました。ズーム インは、スクロール中にズーム用のキーボード ショートカットを押した場合にのみ発生します。
- トランジション ツールを使用して簡単にトランジションを作成することができます。
- ズームインおよびズームアウト機能が改善されました。
課題の作成者の記録
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. You can also search for issues by creator.
新しい "attachments" JQL フィールド
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.
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.
Internet Explorer 11 supported
Internet Explorer 11 is now supported.