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

You can view an issue on the Planning Board and Task Board in three different ways, called 'Views':

  • 'Summaries' view — shows a summary card for each issue
  • 'Cards' view — shows a detailed card for each issue
  • 'List' view — shows each issue as a row in a table

For easier management of pending issues (that is, those which have not been assigned to a child version or component), you can also apply 'visual' issue filters to these views, to exclude child versions or components from your view. These 'Quick Filters' are available on both the Planning and Task boards.

(info) 'Quick Filters' only affect the cards that appear on the current board. Unlike context filters, these filters do not affect the values presented in the Statistics Column.

Your project administrator can configure the information that is displayed for an issue in each of these views. See Configuring your Card Styles for more information.

(tick) Tip: You can also change the viewing 'mode' of the Planning Board to view issues categorised by project, version, component or assignee. See Using Planning Board Modes to View Issues for more information.

To change your issues view,

  1. Log into JIRA.
  2. Navigate to either the Planning Board or Task Board:
    • Click the 'Agile' link's down-arrow in the top navigation bar and select 'Planning Board' from the resulting dropdown menu. The 'Planning Board' will be displayed.
      または
    • Click the 'Agile' link's down-arrow in the top navigation bar and select 'Task Board' from the resulting dropdown menu. The 'Task Board' will be displayed.
  3. Click the 'Views' menu and click the desired issues view from the dropdown menu. The following issue views will be available:
  4. To apply Quick Filters, click the Quick Filters icon at the top left of the board to expand the available issue filter options, and choose your preferred filters by selecting their check boxes:
    • 'Only My Issues' — Excludes any issues that are not yours.
    • 'Hide Sub-tasks' — Excludes any JIRA sub-tasks from appearing on the board.
    • 'Only Pending Issues' — (Planning Board only) Excludes any issues that are part of a child version or component.
      (tick) When at least one filter is applied to a board, the Quick Filter icon appears filled .

Inline editing is available in all views ('Summaries', 'Cards' and 'List'), saving you significant time when actioning issues.

Click the icon (which will appear when you hover over the Issue Type or Priority icons) to display a drop-down menu containing actions relevant to the Board you are looking at, e.g. for the Planning Board you would see the following options:

  • Update Priority --— Click to edit the Priority field for this issue.
  • Add Sub-task — Click to add a sub-task to this issue (if sub-tasks are enabled).
  • Edit in JIRA — Click to open the JIRA 'Edit Issue' screen, on which all issue fields are available for editing.
  • Flag — Click to flag this issue for special attention.
  • Comment — Click to quickly add a comment to this issue.
  • Delete — Click to delete this issue.

Detailed Cards

 

The detailed card is a detailed view of the issue, and presents more information than the summary view.

Screenshot: Issue — Card View

Summaries

 

The summary card is a compact view of the issue. The purpose of this view is to display the most important fields of an issue in a card-feel form.

Screenshot: Issue — Summary View

一覧

 

The list view is essentially viewing the issues as rows in a table. The issue will simply be represented as a single row.

This view is useful when 'ranking' issues, as it is the most compact view.

Screenshot: Issues — List View

Why are there symbols on my cards?

GreenHopper can display symbols on your cards to indicate that there is important information about an issue that you need to be aware of:

  • A (tick) symbol indicates the issue is assigned to multiple fix versions and that at least one of those versions is released. A common scenario would be where an issue is assigned to a sprint (e.g. 'Version 1 Milestone 1') for a version (e.g. 'Version 1'), and the sprint has been completed.
  • A (warning) symbol indicates that somebody has flagged this issue for attention. Read more about flagging fields.





Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.