Documentation for GreenHopper 6.1.x. Documentation for other versions of JIRA Agile is available too.
GreenHopper is now called JIRA Agile. Learn more.

2013 年 2 月 25 日

This release delivers the following enhancements:

Search for Issues by Epic Name

We are pleased to announce that you can now find issues in a given epic by simply using the epic's name in your JQL search, e.g.:

"epic link" = Jupiter

You can still use the epic's issue key (as previously) if you wish, e.g.:

"epic link" = ANERDS-317

(info) Please note that your administrator will need to re-index JIRA before you can search by epic name.


^top

View the Epic Report

エピック レポートは、エピックの完了課題、未完了課題、非見積課題の一覧を表示します。このレポートは、特に複数のスプリントにまたがるエピックの作業を計画するのに役立ちます。

エピック レポートを使用して、エピックの完成に向けた進捗状況を時間の経過とともに把握し、未完了課題または非見積課題といった残りの作業量をトラッキングします。

^top

Right-Click to Quickly Rank and Assign Issues to Sprint

Managing your project's backlog just got a whole lot easier. You can now select one or more issues and right-click to send them to a particular sprint, or to the top/bottom of the backlog.

^top

View Selected Issues in Issue Navigator

From Plan mode, you can now easily jump to the Issue Navigator and view/action your selected issues (see screenshot above).

^top

一括変更

Need to edit, transition, delete or move a bunch of issues? From Plan mode, you can now perform a JIRA Bulk Change on your selected issues (see screenshot above).

^top

Add more Fields to the Issue Detail View

In GreenHopper 6.0.3 we introduced the ability to add text-fields to your cards; in 6.0.5, we added numeric fields; and in 6.0.8, we added date/time fields.

In 6.1.2, you can now also add custom fields of the following types:

  • ラベル
  • [切り替え] を選択すると、
  • check-box
  • ラジオ ボタン
  • VERSION (バージョン)
^top

Exclude Weekends from Cycle Time calculations

By (very) popular request, you can now exclude weekends from your cycle time (that is, the time taken to resolve an issue).

For most teams, including the weekend will artificially inflate your actual cycle time. So now, when viewing the Control Chart, you can simply choose to exclude your non-working days:

^top

 

Search for Sprint by Name

We are pleased to announce that you can now find issues in a given sprint by simply using the sprint's name in your JQL search, e.g.:

sprint = "February 1"

You can still use the sprint's numeric ID (as previously) if you wish, e.g.:

sprint = 123

(info) If you have multiple sprints with similar (or identical) names, you can simply search by using the sprint name — or even just part of it. The possible matches will be shown in the autocomplete drop-down, with the sprint dates shown to help you distinguish between them. (The sprint ID will also be shown, in brackets).

^top

See an Epic's Stories when viewing in JIRA

When viewing an epic in JIRA, you can now see a list of stories (issues) that belong to the epic:

^top

Add more fields to the Issue Detail View

In addition to being able to add custom fields to the Issue Detail View, you can now add most of the JIRA built-in fields — Status, Environment, Component(s), Assignee, etc.

^top

Migrate your old Epics

If you were previously using epics on the Classic boards, you will be pleased to hear that it's now very easy to migrate your epics to your new boards.

For details please see Migrating Epics.

^top


Create Issue when viewing an Epic in JIRA

You can now click the "+" icon, at the top right of the Issues in Epic section, to conveniently add more issues to an epic when viewing an epic in JIRA:


Note that you can also still use the Create issue in epic link in Plan mode (as previously):

^top


 





 


 

  • ラベルなし