Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].

(info) Note that this page only applies if you are using the Classic Boards (which are no longer being actively developed; read more).
To plan versions, epics and sprints on the new boards, please see Using Plan Mode.

 

The Classic Planning Board enables you to prioritise and schedule issues. Issues are represented as cards, colour-coded according to issue type (e.g. Story, Bug, Task, Improvement, etc). Version, component and assignee information is summarised at the right of the Classic Planning Board, allowing you to quickly gauge the backlog for each. Project administrators can add new versions on the Planning Board, to create product, release and sprint backlogs.

You can also manage cards (issues) via the Classic Planning Board. Issues can be easily scheduled and prioritised by dragging and dropping them. You can also perform common JIRA tasks, such as adding, updating and deleting issues (provided you have the appropriate JIRA permissions).

To view the planning board for your project,

  1. Login to JIRA.
  2. Select Agile > Classic in the top navigation bar. Then select Classic Planning Board from the drop-down below the project name.
  3. Select your project from the project dropdown in the top left of the planning board (above the Planning Board dropdown), if it is not already selected. The Planning Board will refresh with information for your project.

Screenshot: GreenHopper Classic Planning Board (click to view larger image)

The screenshot above shows an example Planning Board. To learn more about each part of the Planning Board, please see the sections below and the documentation linked from those sections.


 

On this page:

この章の内容:

関連ページ

 

Planning Board — Navigation Bar

Planning Board - Navigation Bar

  1. Board dropdown — Select another board to view (Task Board, Chart Board or Released Board).
  2. Project dropdown — Select the project whose issues you wish to view.
  3. Context dropdown — Select the context by which to filter issues ('Default', 'On the fly', or other contexts you have created). You can also select Manage to edit your existing contexts, or New to create a new context. Read more about contexts in Using Contexts to Filter and Highlight Issues.
  4. Refresh icon — Click the icon to reload the contents of the Planning Board.
  5. Viewing Mode dropdown — Select the viewing modefor your Planning Board:
    • プロジェクト
    • コンポーネント
    • バージョン
    • 担当者
  6. Viewing Mode sub-dropdown — Select the sub-category of the viewing mode. Read more about viewing modes in Using Classic Planning Board Modes.
  7. New Card — Click the New link to create a new card (i.e. issue). For details see Creating an Issue in GreenHopper Classic.
  8. Views dropdown — Select from the following:
  9. Tools dropdown — Select from the following:
  10. Pagination — Click a page-number to go to the desired page. To configure the number of issues shown per page, see Managing your User Preferences for the Planning Board tab.
  11. Quick Filters— Click the following filters to refine the collection of displayed cards:
    • Only My Issues — Only display issues which are assigned to you.
    • Only Pending Issues — Exclude any issues that are part of a child version or component. (This filter is available on the Planning Board only)
    • Hide Done Issues — Only display issues which have not yet been resolved.
    • Hide Sub-tasks — Only display issues which are not sub-tasks of other issues.
      (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.
  12. Search — See Searching for Issues on a Classic Board.

Planning Board — Issues

Planning Board - Issues
  1. Released — The icon indicates that this issue was resolved in a sub version that has been released, but it is still shown in the parent version as it is assigned to that version as well.
  2. Flagged — The icon indicates that this issue has been flagged for special attention.
  3. Issue Type and Priority — These two icons indicate the Type of this issue (e.g. Task, Bug, Improvement, etc) and its Priority (e.g. Critical, Major, Minor).
    Click the icon (which will appear when you hover over the Issue Type or Priorityicons) to display a drop-down menu containing:
    • 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 as Impediment — Click to flag this issue for special attention.
    • Comment — Click to quickly add a comment to this issue.
    • Delete — Click to delete this issue.
  4. Issue Key --— Click to view the details for this issue.
  5. Editable Fields — Click the icon (which will appear when you hover) to edit the following fields:
    • 要約
    • 修正対象バージョン
    • 担当者
    • ステータス
  6. Sub-tasks — Click to display a dialog box showing the issue's sub-tasks. You can drag-and-drop subtasks within this box to re-order them.
  7. Work Logged (if applicable) — the amount of time that has been spent on this issue. Click to log work on this issue.

Planning Board — Statistics Column

To select a box, click inside it and once selected, the box turns yellow. The content on the rest of the Board you are viewing will be updated to show the data associated with that box.

Planning Board - Versions
  1. 'Add' (Planning Board in 'Version' mode and Chart Board only. Visible to administrators only.) — Click to create a new version. Read more in Adding a Version.
  2. 'Statistics' (Planning Board in 'Version' mode and Chart Board only. Visible to administrators only.) — Click to configure statistics displayed in the boxes in this column. Read more in Configuring a Custom Statistic.
  3. 'Collapse' — Click the icon to show only the title of each box in the Statistics column.
  4. 'Expand' — Click the icon to show the full details for each box in the Statistics column.
  5. 'Hide' — Click the icon to hide the Statistics column and display the 'Issues' section of the Board in full screen width.
  6. Name ('Version', 'Assignee', 'Component', 'Project Overview' modes only. Visible to administrators only.) — Click the icon (which will appear when you hover this area of the selected box) to edit the version or component name.
  7. Actions menu — Click the icon (which will appear at the top right of the selected box when you hover over this area) to display a drop-down menu. This drop-down menu can contain the following items. Be aware that some of these are not available on certain Boards:
    • 'Toggle visibility' — Click to show/hide the current box in the Statistics column.
    • 'Issue Navigator' — Click to go to the JIRA Issue Navigator.
    • 'Go to Task Board' ('Version' mode only) — Click to go to the Task Board.
    • 'Go to Planning Board' ('Version' mode only) — Click to go to the Planning Board.
    • 'Go to Chart Board' ('Version' mode only) — Click to go to the Chart Board.
    • 'Non Working Days' ('Version' mode only. Visible to administrators only.) — Click to edit the Non Working Days for a specific version. (Note: to edit the Non Working Days for all of the Classic boards, see Specifying your GreenHopper General Configuration.)
    • 'Print Cards' (Planning Board in 'Version' mode only) — Click to print the displayed issues. For details please see Printing Issues in Card Form.
    • 'Print Chart' (Chart and Released Boards only) — Click to print the currently viewed chart.
    • 'Excel (Chart Data)' ('Hour Burndown Chart' on the Chart Board only) — Click to download a csv version of the chart's data.
      (info) You may need to refresh the contents of the chart board first in order to see this menu option.
    • 'Release' ('Version' mode only. Visible to administrators only.) — Click to release the version. A snapshot of all of the charts associated with this version will also be captured (before any issues are swapped). You will be able to access these snapshots via your Released Board.
      (info) If the version contains unfinished issues, you will be prompted to either ignore them and proceed with the release, or move the unfinished issues to another version of your choice.
    • 'Recompute' (Released Board only; 'Project Overview' mode only. Visible to administrators only.) — Click to refresh the Released Board. (Note: the Project Overview is the only chart that is stored statically; all other charts are generated dynamically.)
    • 'Create Wallboard' (Planning Board only; 'Project Overview' mode only) — Click to create a Wallboard.
      1. A Wallboard will be created with the name '<Project name> (autogenerated)' and displayed. Your wallboard is a new page on your JIRA dashboard (see Customising the JIRA Dashboard), and will contain:
      2. Select 'View as Wallboard' from the 'Tools' drop-down on your JIRA dashboard, and stare in awe at your fresh new wallboard. For optimal use of screen real-estate, enter full-screen mode on your browser (F11 in Firefox 3.6 and Chrome 5; Safari requires a plugin to enable full-screen mode) and refresh. Wallboards are optimised for 1920x1080 and 1920x1200 screens, but should work in some other resolution modes.
  8. Progress of the version ('Version' mode only) — the green bar indicates the percentage of issues that are complete, the yellow bar indicates the percentage of issues in progress, the red bar indicates the percentage of issues that have not been started. Hover over the bar to see the exact percentages. Click on a coloured section of the bar to be taken to the JIRA Issue Navigatorfor the full list of issues in that colour.
  9. 'Parent' ('Version' & 'Component' modes only) — Click the icon (which will appear when you hover, if you are an administrator) to choose the parent version or component for the version. All issues under the version/component will also be a subset of the parent version/component, e.g. 'Version 1' could be set as the parent version of 'Version 1 milestone 1'. Read more in Setting Up a Component Hierarchy and Setting Up a Version Hierarchy.
  10. 'Start date' ('Version' mode only) — Click the icon (which will appear when you hover, if you are an administrator) to edit the start date for the version.
  11. 'End date' ('Version' mode only) — Click the icon (which will appear when you hover, if you are an administrator) to edit the end date for the version.
    (tick) Tip: The start date and end date are used to compute the various Classic charts.
  12. 'Release date' ('Version' mode only) — Click the icon (which will appear when you hover, if you are an administrator) to edit the JIRA release date for the version.
  13. Issue Type statistics — A summary of the number of issues of each type.
  14. Statistics based on the Task Board mapping — A summary of the number of issues in each status (based on the Mappings that your administrator has specified in the Task Board Settings).
  15. Time-tracking statistics:
    • 'Time Remaining' — Click the icon (which will appear when you hover, if you are an administrator) to specify maximum and minimum limits for the amount of time remaining.
  16. Custom statistics — Displayed if any custom statistics have been created by the project administrator. (The red numbers, if shown, indicate that a statistic's constraint has been exceeded.) If custom statistics exist, you can click the icon to add them as markers on your Planning Board (see Using Statistical Markers to Group Issues).

(tick) Tip: Boxes that relate to child versions or components are attached below their parent version or component and are represented with a right-indented arrow, as shown by the 'Hardening Sprint' example in the screenshot above.

The content of the Statistics Column will differ depending on the viewing mode selected. For example, when 'Version' mode is selected (as shown in the image above), the Parent, Start Date, End Date and Release Date fields will be shown, and the Add button will appear at the top of the column. You can read more about about viewing modes in Using Classic Planning Board Modes.

29 Comments

  1. Anonymous

    Feb 17, 2011

    How are the versions sorted in the statistics column?  I would like them to align with how they are scheduled when I view the ordering set up in JIRA's version management, but they don't seem to correlate.

    1. Anonymous

      Mar 14, 2011

      I have the same question.  The problem is that I would like my most recent iterations (versions) to appear at the top of the list - instead of the bottom (which forces me to "scroll" / page down).  Changing the order of versions in the Manage Versions page does not seem to affect the order they are displayed on the Planning Board.

    2. Anonymous

      May 31, 2011

      Agree. If you set up your version>iteration/sprint hierarchy like the documentation says to, the current iteration never shows at the top. You can collapse all, then toggle visibility for your selected iteration, but why on earth doesn't it respect the schedule set in project>versions>manage_versions?

    3. Confusion

      Mar 28, 2012

      I would also like to know how they are ordered. We tend to name a version 'Release 1' and have sub-versions 'Iteration 1.1', 'Iteration 1.2', etc. Start, stop and release dates are of course 'in order'. So it seems they aren't ordered alphabetically or by date. It would be great if they would be ordered in some way.

  2. Charlie Trotter

    Jun 16, 2011

    We're using a custom issue to type for solution gaps and cannot get any issues of this type to be available on the Planning board. Is this a configuration issue or are only 'vanilla' issue types like stories/tasks able to be displayed. thanks. 

    1. Nicholas Muldoon [Atlassian]

      Jun 20, 2011

      Hi Charlie,

      Please ensure that your issue type is associated with the project, it will then be available within Tools -> Configuration -> Card Styles.

      Thanks Charlie.

      Regards,
      Nicholas Muldoon

      1. Anonymous

        Jul 21, 2011

        We have the project configured for GreenHopper and Tools -> Configuration -> General is configured Project Template = Scrum

        I have ensured that the Tools -> Configuration -> Card Styles contains Epic, Story, Technical Task, Bug, and Improvement.  

        However, when I use the Planning Board (or anywhere else, really) and choose New Card (or look anywhere in the dropdown of issue types), I only have choices for Epic, Story, Bug, and Improvement.  I need Task or Technical Task.  When I went to the Tools -> Configuration -> Card Styles and changed the configuration for card background, for example, it is reflected in the planning board, so I know the changes are taking effect.  Why can't I get a Task or Technical Task as a choice in my dropdown of issue types?

        1. Anonymous

          Aug 01, 2011

          I believe technical task is a sub-tasks, so it will only show up as the type of issue if you are creating a sub-task for a particular issue type. Task is a standard issue by default, so that should be appearing unless an system administrator has changed them around.

  3. Anonymous

    Jun 24, 2011

    Can someone tell me how I organise the Planning Board view so as to show not just parents and subtasks, but other kinds of "nested" link relationships, like Consists of or Part of?

    This seems like such an obvious feature to have, but I've never managed to find out how to produce it.

  4. Amul Shah

    Aug 08, 2011

    How can I specify vacation (non-working) days per contributor?

  5. Anonymous

    Oct 13, 2011

    The time statistics for a given version do not seem to calculate correctly. Maybe it is something that happens when tasks are moved between versions? I cant figure this one out and it is an important feature to easily get a view on how much work are in the version, how much time is spent, and how much time remains. Now I have to calculate this manually by going through every task in the version. 

    Any help on this will be greatly appreciated

    1. Anonymous

      Oct 24, 2011

      I have the same problem. We drag and drop the unfinished stories to the next sprint. Sprints are "sub versions" of larger releases. Our statistics are totally %*€&#@!.

      I can not make sense of all this. Traditionally JIRA issues do not know about "time". Log work logs work and estimates are estimates, versions can be changed and everything looks alright. However somehow GH "automatically" assumes more based on what was assigned to where and when was something done? ... Makes the whole statistics thing unusable at least in our case. Maybe we are just using it wrong, but I can't figure out why. Duplicating issues doesn't make sense to me either.

    2. Anonymous

      Dec 21, 2011

      Release the sprint instead of moving the unfinished issues to the next sprint.  When you release a sprint in the planning board, Greenhopper will notify you that you have unfinished issues and ask you which version you want to move them to.  This will preserve your stats and allow you to move your issues.

  6. Anonymous

    Jan 06, 2012

    How can I get a sorted view on my product backlog? I scheduled the stories to iterations (with dedicated start and end), but the backlog in the planning board view appears unsorted (time schedule is not considered?). Besides this I would like to see more details like assignee and story points in this view.

  7. Anonymous

    Feb 02, 2012

    I'd like to be able to "Hide Done Issues" and "Hide Sub-Tasks" as an anonymous (not logged in) user.  However, I only see those buttons when logged in.  Is there a reason for that?

  8. Philip DeLuca

    Apr 03, 2012

    A couple of planning board questions:

    1. How do I filter issues by priority when the Planning board is set to show versions? I want to take all tasks that are, say, priority 1 and assign them to a release, say, "release 1."
    2. How do I bulk change all of the tasks I do want to move to a particular version? This may be better-directed at the advanced search topic, but if I search for all tasks that have "priority 1" and attempt to bulk change them to "release 1" it of course doesn't provide an option to do that. AffectedVersion doesn't help - since I want the planning board to show only the tasks due for a given release and affectedVersion doesn't change the version with which a task is associated.

    At the moment all unscheduled tasks appear in the card list and I have to manually find the ones with the proper priority and move them into the version. Since I have over a hundred tasks that meet this criteria, I figure I'm missing something really obvious.

  9. Anonymous

    Apr 06, 2012

    Why can't I move the tasks on my planning board or rapid board? They move but don't stay where I place them. Help!

  10. Anonymous

    Apr 24, 2012

    We are using the scrum template and schema and would like to assign tasks to the stories.  We have moved task to the scrum schema.  However, stories and tasks seem to only be connected to an epic or theme.  Any work around for this?

  11. Anonymous

    May 16, 2012

    I have the same problem as the poster two above me from April 6th. No matter what I do, on the planning board, dragging the items around is meaningless (except to move them into a different release).  There appears to be no way to manually order tasks on the planning board. On the rapid board I can drag them into position. Is this the correct (intended) behavior, that the rapid board is the only place to actually order our tasks? 

  12. Anonymous

    May 23, 2012

    I have the same problem as the poster two above me from April 6th, May 16.

    When will we have a fix on this point.

    1. Anonymous

      May 27, 2012

      We are having the same issue.  Luckily we were just evaluating Green Hopper, because this was one of the primary goals we wanted to get out of using Green Hopper rather than just Jira.  We avoided paying for 400 users for a broken feature!

      Any ideas on how to fix this?

      1. Nicholas Muldoon [Atlassian]

        May 27, 2012

        Hello, 

        If you ever get stuck in future don't hesitate to raise a support request for immediate assistance.

        It sounds like you don't have the Default context (or your currently selected context) sorted by Rank. Click the Context drop down, then Manage. On the left hand side you will see Sort, make sure you have that set to the Rank field - as that is the only one that will enable you to drag and drop to order the backlog.

         

        Thanks,
        Nicholas Muldoon 

  13. Anonymous

    Jul 05, 2012

    Hi

    We work on several versions of our software in each sprint. One that's already in the field and one that has not been released. For example when an issue is created it will have 5.0 and 5.1 put into the fix version fields.

    In the planning board we move the issue into sprints, for example Sprint 5.

    I would like Sprint 5 to be added to the Fix version but it actually removes 5.0 and 5.1.

    Could you tell me why it behaves in this way please?

    Many thanks

    1. Anonymous

      Jul 05, 2012

      Did some more digging and I see this not will be fixed in the Planning board but you suggest people use the Rapid board as at V5.10. for scrum.

      Can you tell me when Greenhopper 6.0 will be released as I might wait for that?

  14. Nicole Hushka

    Oct 08, 2012

    In this documentation page you indicate that I should be able to use "More Actions" to get to the planning board from within a ticket in 6.0.  This seems to have gone away and now leaves us in a painful navigation situation.  Is it possible, or is this documentation incorrect?

    Snipped from above...

    Tip: you can also jump directly to the Classic Planning Board when viewing an issue in JIRA, by selecting 'Planning Board' from the 'More Actions' menu.

     

    1. Rosie Jameson [Atlassian]

      Oct 15, 2012

      You are right - this feature has been replaced by the "View on Board" feature.

      Sorry for the inconvenience.

  15. Anonymous

    Jan 02, 2013

    Could you make the rather useful "Statistics Column" visible in the other views such as the Task Board? 

  16. Teresa Fraczek

    Apr 18, 2013

    hi since this classic board is discontinued from further developement, what is the equvalent option for planning in the new reseases?

    1. Rosie Jameson [Atlassian]

      Apr 19, 2013

      Please see Using Plan Mode



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.