JIRA 6.1 Beta 1 Release Notes

2013 年 8 月 26 日 

Atlassian is proud to present JIRA 6.1 Beta 1.  This public development release is part of our Early Access Program (EAP) leading up to the official JIRA 6.1 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 here.

 JIRA 6.1 Upgrade Notes

Key features

Create workflows and fields with ease

新しいワークフロー デザイナー

JIRA has a new workflow designer – it loads quickly, scrolls easily, and lets you build and edit workflows faster than ever. The designer view also appears in view issue, one of our highest voted feature requests.  

Workflows are one of the tools in JIRA that provide it with its amazing flexibility and we want to ensure that workflow creation and management is the best in its class. Making sure that all of our users (JIRA administrators to our most casual users) understand workflows is one of our biggest design and feature improvement goals. Look for more changes in this area in the near future.

ハイライト

• Full screen mode!
• Workflow viewer shows the transition lines as they are drawn using the Workflow Designer, another big feature request.
  
• Incoming and outgoing transitions relevant to each status are displayed.
• Global transitions are now first class citizens in the designer.
• Geometric snap lines (snap to other statuses!).

課題の閲覧中にカスタム フィールドを追加する

JIRA 管理者は、課題の表示中に課題タイプにカスタム フィールドを追加したり、そのカスタム フィールドのオプションを構成できるようになりました。近日中に、既存のフィールドの追加機能も実装予定です。

Custom fields are another powerful JIRA tool that enable JIRA administrators to quickly customize the way issues look, to fit your company's process. This new way of adding custom fields is much simpler, making the entire experience fast, effective, and powerful. Not only do we add the field to the View screen, but we add it to the Create and Edit screens as well. This means you can edit the field you just created instantly, and input data into that field the next time you add an issue.

また、カスタムフィールドの作成時に、タイプを「標準」または「詳細」から選択できるようになりました。標準タイプでは各タイプのプレビューを表示できるため、作成中にイメージを見ることができます。これにより、希望するカスタムフィールドをより早く取得できます。

続きを読む

New project templates

シンプルな課題トラッキング プロジェクト

This project provides you with a quick and easy way to get JIRA up and running for simple issue tracking. This project is aimed at users who want to track their issues through a simple three-step workflow, while taking advantage of JIRA's other powerful features. Later on, it's easy to extend to other, more complex workflows provided by JIRA.

For more details on this project template, see Simple Issue Tracking project.

Software Development project

This project provides you with an easy to use template for software development. It includes a simple workflow with statuses representing tasks that go through a development and review process. You can later customise this further to suit your team's evolving processes.

For more details on this project template, see Software Development project.

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.

If you use these features, we'd love to hear what you think!

The ability to create feature branches will be available in Stash at the end of September.

A feast of usability improvements

Continuing on from JIRA 6, the JIRA 6.1 release improves usability in a number of areas, described below.

Easier issue navigator column configuration

JIRA lets you change the columns of the table of search results for any search results displayed using the List view (as opposed to the Detail View). Click Columns at top right of the issue table to open the column configuration dialog, shown below.

続きを読む

Updates 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.

メール通知の外観の変更

Jira のメール通知が改善されました。詳細については、こちらを参照してください。

New default workflow

We've simplified JIRA's out-of-the-box experience, with new, better defaults to make issue tracking quick and simple. Previously, the JIRA default workflow required you to be the assignee in order to move an issue from one status to another, this is no longer the case. Anyone can transition issues and the assignee field will automatically be updated to that user.  You can always change back to the old behavior, or just import the Classic Default JIRA Workflow from Marketplace

新しく作成されたすべての課題が既定で未割り当てに

JIRA レポートに素早くアクセス

You can now access JIRA reports directly from its own tab under the Browse Project page.

New whitelist for JIRA

JIRA's whitelist is now more intuitive and easier to configure. Read more...

Enterprise Enhancements

Change usernames in LDAP

JIRA now supports changing usernames when connected to an external LDAP user directory. Previously, if you changed the name of a user in LDAP, JIRA would interpret that as deleting and adding a user. This wouldn't work because of the data associated with the user. Now, it will be correctly treated as a rename.

For most LDAP implementations, this will work out of the box. However, in a very small minority of cases, you may need to configure the LDAP settings in JIRA: read more.

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. Read more...

Additional Improvements and Changes

JIRA アドオンの名前の変更

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 UI 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.