Index
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
課題を表示するには、いくつかの方法があります：
Quick View in GreenHopper
ボードを表示しながら、課題詳細の一部を表示する手順は、次のとおりです：
- 上部ナビゲーションバーで Agile リンクの下矢印をクリックし、表示されるドロップダウンメニューから目的のボードを選択します。
- Scrum を使用中で、課題が現在計画段階にある場合は、「計画」または「作業」をクリックします。
- 課題キーをクリック (または作業モードで t と入力) して、画面の右側に課題詳細ビューを表示します。
You can close the Issue Detail View by clicking the 'x' icon (or typing 't').
The Issue Detail View may look different to the screenshot below if it has been customised.
On this page:
スクリーンショット 1 ：課題詳細ビュー
タブの凡例
| タブ | クリックすると... |
|---|---|
 | 課題詳細ビューのサイズ変更 |
 | 課題の詳細表示： |
 | 課題の説明フィールド表示 |
 | 課題についてのコメント表示 |
 | 課題に添付されたファイルの表示 |
 | 課題のサブタスクの簡易な要約表示（および簡単に新規のサブタスクを作成するボタン） |
 | View any test sessions for this issue (if you are using Bonfire). |
 | View any commits for this issue (if you are using the DVCS Connector). |
JIRA での課題表示
To view all of an issue's fields (that is, the JIRA issue screen),
- 上部ナビゲーションバーで Agile リンクの下矢印をクリックし、表示されるドロップダウンメニューから目的のボードを選択します。
- Click the issue key (or type t) to display the Issue Detail View (see above).
- 課題詳細ビューで、課題キーをクリックするか、「 o 」を入力して、課題のフィールドをすべて表示します。
または、Ctrlキーを押しながら、ボード上の課題キーをクリックして、JIRA 課題表示画面を新しいブラウザタブで開きます。
スクリーンショット3 ： JIRA 「課題表示」画面
The Agile panel (bottom right of screen) contains sprint information. If the Issue is in an active or completed sprint then the sprint name is shown, along with the end date of the completed sprint. Clicking the sprint name will allow you to view the relevant sprint details; for active sprints this will take you to the Work mode (with focus on the relevant issue), or for a completed sprint, you will be taken to the Sprint Retrospective Report.
When viewing an issue within JIRA, you can also jump to the relevant GreenHopper board(s) by selecting More Actions > Rapid Board or clicking the View on Board included in the Agile panel.
JIRA 課題ナビゲーターでの複数課題表示
To view multiple issues as a list in the JIRA Issue Navigator,
- 上部ナビゲーションバーで Agile リンクの下矢印をクリックし、表示されるドロップダウンメニューから目的のボードを選択します。
- Your board will be displayed. Click 'Plan'.
- 課題（複数可）を選択（ Shift + Click または Ctrl + Click ）して右クリックし、課題ナビゲーターを選択します（下のスクリーンショットを参照）。
Screenshot: right-clicking an issue in 'Plan' mode
Excel へのエクスポート
スプレッドシートで課題を表示する手順は、次のとおりです。
- 上部ナビゲーションバーで Agile リンクの下矢印をクリックし、表示されるドロップダウンメニューから目的のボードを選択します。
- Your board will be displayed. Click 'Plan'.
- 課題（複数可）を選択（ Shift + Click または Ctrl + Click ）して右クリックし、 Excel にエクスポートを選択します（上のスクリーンショットを参照）。
概要
コンテンツ ツール
アプリ
Log a request with our support team.
Raise an issue for our developers.
See answers from the community.
Tweet, blog and update our documentation.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.
12 Comments
Axel Kratel
Jan 08, 2012I have exactly the same issue as Dave above. We just upgraded to the latest GreenHopper in order to get access to the new rapid board. To my dismay, NONE of the custom screen configurations from JIRA show up. What's up with that? For example, our User Stories have two fields, "Description" and "Acceptance Criteria", but the "Acceptance Criteria" custom field doesn't show up in the issue view for the Kanban board. Can you imagine trying to look at user stories and not have access to the acceptance criteria?
I have to express a great deal of frustration with Atlassian, your product management team doesn't seem to have much focus on basic usability, it seems completely overlooked in all of your products. At this stage, we will probably only make very limited use of the Kanban board to get some sort of birds' eye view.
As a former Rally user at my previous company, I have to say I really, really miss Rally and it's user friendliness. All the agile functionality for requirements in JIRA/Greenhopper seem pretty much like an afterthought, a hack. it works, but it doesn't work in a frictionless manner. A bug is NOT a user story, requires different fields and has a completely different lifecycle. No one at Attlassian seems to be cluing in on that fact.
Rosie Jameson [Atlassian]
Feb 24, 2013Hi Axel, the Issue Detail View is now customisable. Please see Configuring the Issue Detail View.
Francois Groleau
Mar 28, 2012Is it possible to control how the Details view is displayed? For instance, I would like to remove the Details, Description and Comments tab and see all the information in a single "tab".
Also, the explanation for the series of dots across the bottom of the cards should be added to the documentation. I have searched quite a bit to find it buried in the comments
.
Anonymous
Jun 08, 2012In addition to removing those options I'd like to be able to set one as a default.
Anonymous
Sept 03, 2012Hi,
please make it possible to set as admin which view should open per default; meaning the admin can decide if the new quick view (no attachments or custom fields displayed) or the JIRA issue screen will open.
The actual quick view screen is a massiv productivity drawback and i am really puzzled about your implementation.
Alex
Daniela Silva
Sept 10, 2012Hi Rosie, Alex and Dave,
For a scrum project is very important the Acceptance Criteria field (it's a free text style), but in the first version of greenhopper that I'm using is not available for my surprise, then I have created as a custom field.
But today I did the upgrade for the last version of greenhopper and the boards change, you discovered a way to configure to show de custom field "Acceptance Criteria" in the right pane "Detail View of an issue" ?
Karie Kelly
Sept 12, 2012Why is the add text appear as a link, but is disabled in the following reference: "Status, Component, Labels, Affects Version and Fix Version, plus any fields you have added"?
Based on comments, this does not seem valid as fields that i have added to these screens don't appear here.
Anonymous
Jan 30, 2013I accidentally closed the Issue Detail view by clicking the X on it. How do I get it back?
Anonymous
Jan 30, 2013Click on another issue.
Lisa Rahder
Jun 06, 2013How do you view a closed issue?
Rosie Jameson [Atlassian]
Jun 14, 2013You can query for closed issues using JQL, via the Issue Navigator. If the requirement is to see recently closed issues, you can set the last column to show issues which are closed and have been updated in the last 3 days say, so that they show for a while (when it's relevant) and then disappear automatically.
Tom Murton
Jul 22, 2013so if a story is in a sprint but that sprint isnt active (as its not started) is it shown anywhere in the issue? we have big problems with a story is in a sprint (shown on planning board) but as that sprint hasnt started then we cant see it anywhere in the issue.