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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 131 Next »

Updated for GreenHopper 5.10 so it is now easier than ever to get up and running with GreenHopper.

Welcome to GreenHopper 101, an introductory guide to the GreenHopper plugin for JIRA and a tour of the most interesting GreenHopper features. Use this page to guide your evaluation process or quickly get up to speed with GreenHopper.

The intended audience for this document is software developers who are familiar with Agile methodologies.

Getting Started

First things first. If you haven't already got the GreenHopper plugin up and running, carry out the following steps.

1. Installing GreenHopper

  1. Log in to JIRA as a user with the 'JIRA System Administrators' global permission.
  2. Click the 'cog' icon on the top bar (or click Administation if using an older version of JIRA) and select Add-ons. The Universal Plugin Manager (UPM) page will be displayed.
  3. On the Find new add-ons page, type 'GreenHopper' in the search box.
  4. The GreenHopper add-on will appear in the list below the search box. Click the Install button. A confirmation message and the add-on details will display, if it is installed successfully.

  1. Log in as a user with the 'JIRA System Administrators' global permission.
  2. Click the 'cog' icon on the top bar (or click Administation if using an older version of JIRA) and select Add-ons. The Universal Plugin Manager (UPM) page will be displayed.
  3. On the Purchased Add-ons page, click Check for Purchases then locate GreenHopper.
  4. Click the Manage button. The details for the GreenHopper add-on will display.
    (info) Your Support Entitlement Number (SEN) is also shown on this screen.
  5. Paste your license into the License Key field and click Update.
    (info) You can copy your GreenHopper license from https://my.atlassian.com, where you can either generate a new Evaluation License Key, or retrieve your old License Key if you already have one.

(info) For more information please see Specifying your License Details.

2. Getting Started: Scrum

Scrum is generally used by development teams who follow a roadmap of planned features for upcoming versions of their product. Scrum teams work in sprints.

  1. Click the Agile menu in the top navigation bar. The Getting Started page will appear.
  2. On the Scrum tab,
    • If someone has already created a Scrum board for you to use, click Open an existing board (in step 2).
    •  Otherwise:
      • If you already have a JIRA project in which to store your Agile tasks, click create a new Scrum board (in step 2). Otherwise, click create a new project and board (in step 1). Type a descriptive Name and unique Key for your project, and select the Project Lead (that is, the person who will manage this project).
        (info) Note that you will need the 'JIRA Administrators' global permission and the 'Administer Projects' project permission in order to create a JIRA project. If you don't have these permissions, you will need to ask your JIRA administrator to create a project for you. For more details, please see the JIRA documentation on Defining a Project.
      • Enter the name of your new board, and select the project(s) you wish to work on.

For more information, please see Creating a Rapid Board.

Many Scrum teams estimate tasks in Story Points, then track tasks using hours. GreenHopper therefore gives you the flexibility to set your estimation and tracking statistics differently, depending on what best suits your team. By default, your Scrum board will use Story Points for estimation, and will also use Story Points for tracking.

To use hours (instead of Story Points) for tracking:

  1. Select Agile > Manage Boards from the top navigation bar.
  2. On the Manage boards screen, click the Configure link corresponding to the board of interest.
  3. On the board Configuration screen, click the Estimation and Tracking tab.
  4. In the Time Tracking field, select Remaining Estimate and Time Spent.

For more information, please see Configuring Estimation and Tracking.

... or ...

Getting Started: Kanban

Kanban is often used by bugfix teams who deliver maintenance releases of their product. Kanban is also well suited to DevOps, Build Engineering and Support teams.

    1. Click the Agile menu in the top navigation bar. The Getting Started page will appear.
    2. On the Kanban tab,
      • If someone has already created a Kanban board for you to use, click Open an existing board (in step 2).
      • Otherwise:
        • If you already have a JIRA project in which to store your Agile tasks, click create a new Kanban board (in step 2). Otherwise, click create a new project and board (in step 1). Type a descriptive Name and unique Key for your project, and select the Project Lead (that is, the person who will manage this project).
          (info) Note that you will need the 'JIRA Administrators' global permission and the 'Administer Projects' project permission in order to create a JIRA project. If you don't have these permissions, you will need to ask your JIRA administrator to create a project for you. For more details, please see the JIRA documentation on Defining a Project.
        • Enter the name of your new board, and select the project(s) you wish to work on.
Creating a Rapid Board

For more information, please see Creating a Rapid Board.

Constraints specify how many issues a column can contain. If the constraint for a column is exceeded, the constraint will be highlighted in red.

To set constraints based on the number of issues in a given column:

  1. Select Agile > Manage Boards from the top navigation bar.
  2. On the Manage boards screen, click the Configure link corresponding to the board of interest.
  3. On the board Configuration screen, click the Columns tab.
  4. In the Column Constraint drop-down, select Issue Count.
  5. To set the columns Max constraint, click the red box at the top of the column, type the new value and press the Enter key. E.g. if your business practice is to have no more than 5 issues 'In Progress' at any one time, you would specify 5.
  6. Close the Use board button (at the top of the page). Your board will refresh with the column constraint applied. If the total number of issues in that column exceeds the maximum capacity, the column will be highlighted in red.

For more information, please see Configuring Columns.

 

3. Using Keyboard Shortcuts

  • click 'a' to assign an issue.
  • click 'l' to label an issue.
  • click 'm' is comment on an issue.
  • click 'z' to display your board in 'Projector' mode (i.e. full-screen).
  • click '.' for the JIRA Operations dialog.

  • click 'j' to go to the next issue (down) in a column on the Rapid Board.

  • click 'k' to go to the previous issue (up) in a column on the Rapid Board.
  • click 'n' to go to the next (right) column on the Rapid Board.
  • click 'p' to go to the previous (left) column on the Rapid Board.
  • click 't' to toggle between hiding or showing the detailed view of the currently selected issue on the Rapid Board.
  • click 'o' to open the issue which is currently showing in the detailed view on the Rapid Board.
  • click 'Enter' to submit the content of a field being edited in the detailed view on the Rapid Board.
  • click 'Shift' + 'Enter' to add a new line to a field being edited in the detailed view on the Rapid Board.

  • click 's' + 't' to move an issue to the top of the current column on the Rapid Board. (Only applicable if Ranking has been enabled.)

  • click 's' + 'b' to move an issue to the bottom of the current column on the Rapid Board. (Only applicable if Ranking has been enabled.)

(info) For more information, please see Using Keyboard Shortcuts.

Planning your Work

4.  Creating an Issue

  1. Click Create Issue at the top of the screen.

  2. Enter your issue details into the 'Create Issue' dialog box.
    (tick) If you select the Create another check box, JIRA will create your issue and automatically pre-populate a new 'Create Issue' dialog box with your previous issue details, while leaving the Summary field blank. This allows you to rapidly create a series of issues with similar details.
    (tick) If you wish to choose which fields will appear when you create (or edit) an issue, click the Configure Fields button.

For more information, please see Creating an Issue.

5. Ranking Issues

In Plan mode (if you are using Scrum):

  1. Click the Agile menu in the top navigation bar and select Rapid Board from the drop-down menu.
  2. Select your preferred Rapid Board, then click Plan.
  3. Rank an issue by dragging and dropping it to a higher or lower position within its current column.

In Work mode (if you are using Kanban):

  1. Click the Agile menu in the top navigation bar and select Rapid Board from the drop-down menu.
  2. Select your preferred Rapid Board, then click Work.
  3. Rank an issue by dragging and dropping it to a higher or lower position within its current column.

For more information, please see Ranking an Issue.

6. Estimating Issues (Scrum)

  1. Click the Agile menu in the top navigation bar and select Rapid Board.
  2. Select your preferred Rapid Board, then click Plan.
  3. Click each issue on the left-hand side of the screen to display its details on the right-hand side of the screen.
  4. Enter an Estimate for each issue by clicking the Estimate field on the right-hand side of the screen

For more information, please see Using Plan Mode.

7. Starting a Sprint (Scrum)

Once you have ranked and estimated your issues, you are ready to start a sprint.

  1. Click the Agile menu in the top navigation bar and select Rapid Board.
  2. Select your preferred Rapid Board, then click Plan.
  3. Make sure the sprint marker (the grey bar) is positioned below the issues you want to include in your new sprint. Drag it up or down as needed.
  4. Click the Start Sprint button.
    (info) You will need to have the JIRA 'Project Administrator' permission in the project(s) whose issues are to be included in the new sprint.
    (info) If you do not have an estimation statistic applied to an issue, you will receive a warning when starting the sprint (unless you are using Issue Count, as this is calculated automatically).
  5. You will be prompted to enter a sprint name and to select the Start Date and End Date for the sprint.
  6. The issues will disappear from Plan mode and move into Work mode. While a sprint is active in Work mode, you can still plan a subsequent iteration in Plan mode, but you won't be able to start it until the active sprint is completed. (You can, however, drag and drop an issue in Plan mode onto the active sprint.)

For more information, please see Starting a Sprint.

Working on Issues

8. Viewing your "To Do" List

  1. Click the Agile menu in the top navigation bar and select Rapid Board.
  2. Select your preferred Rapid Board, then click Work.
  3. If you wish to see only the issues that are assigned to you, click the Only My Issues button.

For more information, please see Using Work Mode.

9. Transitioning Issues through Statuses

  1. Click the Agile menu in the top navigation bar and select Rapid Board.
  2. Select your preferred Rapid Board, then click Work.
  3. Drag and drop the desired card(s) to the column that matches the status to which you want to assign the issue(s).
    (warning) If moving an issue causes a constraint to be exceeded, the affected constraint will be displaed in red (maximum) or yellow (minimum).

For more information, please see Transitioning an Issue.

10. Ending a Sprint (Scrum)

  1. Click the Agile menu in the top navigation bar and select Rapid Board.
  2. Select your preferred Rapid Board, then click Work.
  3. Click the 'Close sprint' icon at the top of the 'Done' (rightmost) column.
    (info) You will need to have the JIRA 'Project Administrator' permission in the project(s) whose issues are included in the sprint.
    (info) When you try to close a sprint, and you have parent issues not Done but all sub-tasks are Done, you will be prompted to make the parent Done before continuing.
  4. You will be taken to the Sprint Report. Your issues will move out of Work mode. Any incomplete issues will move back into the backlog and will be visible in Plan mode.

For more information, please see Ending a Sprint.

Many Scrum teams don't release a version at the end of a sprint, but if you need to, it's easy to do.

  1. In the Completed Issues section of the Sprint Report for your completed sprint, click View in Issue Navigator.
  2. You can then use JIRA's Bulk Edit to assign all of the issues to the relevant version (for details, please see the JIRA documentation on
     Bulk Operations
    ).

... or ...

Releasing a Version (Kanban)

  1. Click the Agile menu in the top navigation bar and select Rapid Board.
  2. Select your preferred Rapid Board, then click Work.
  3. Click the Release icon at the top of the Done (rightmost) column.
    (info) You will need to have the JIRA 'Project Administrator' permission in the project(s) whose issues are to be included in the version.
  4. The 'Release' window will display. Enter the Version name and Release date (optional — will default to today's date).
  5. Click the Release button to save your new version and mark it as 'released' throughout JIRA and GreenHopper.
Creating a Rapid Board

For more information, please see Releasing a Version.

 

Searching and Reporting

11. Tracking Progress: Scrum

A Burndown Chart shows the actual and estimated amount of work to be done in a sprint, and helps you to project the likelihood of achieving the sprint goal.

  1. Click the Agile menu in the top navigation bar and select Rapid Board.
  2. Select your preferred Rapid Board, then click Report.
  3. Select Burndown Chart from the drop-down at left to display the burndown chart.
  4. Any changes to scope (e.g. issues added to sprint, issues removed from sprint) are shown in the table below the graph.

For more information, please see Viewing the Burndown Chart.

A Sprint Report shows the list of issues in each sprint. It is useful for your Sprint Retrospective meeting, and also for mid-sprint progress checks.

  1. Click the Agile menu in the top navigation bar and select Rapid Board.
  2. Select your preferred Rapid Board, then click Report.
  3. Select Burndown Chart from the drop-down at left to display the burndown chart.
  4. Any changes to scope (e.g. issues added to sprint, issues removed from sprint) are shown in the table below the graph.

For more information, please see Viewing the Sprint Report.

... or ...

Tracking Progress: Kanban

A Cumulative Flow Diagram (CFD) shows your work-in-progress and helps you to identify bottlenecks in your processes.

  1. Click the Agile menu in the top navigation bar and select Rapid Board.
  2. Select your preferred Rapid Board, then click Report.
  3. Select Cumulative Flow Diagram from the drop-down at left to display the CFD.

For more information, please see Viewing the Cumulative Flow Chart.

A Control Chart shows you the cycle time (lead time) for your product, version or sprint.

  1. Click the Agile menu in the top navigation bar and select Rapid Board.
  2. Select your preferred Rapid Board, then click Report.
  3. Select Control Chart from the drop-down at left to display the control chart.
  4. Hover over the graph at any point to display actual values of the moving average.

For more information, please see Viewing the Control Chart.

 

12. Filtering Issues

You can use Quick Filters to filter issues on-the-fly, enabling you for example to only see issues of a particular type (such as 'Bug').

  1. Click the Agile menu in the top navigation bar and select Manage Rapid Boards from the drop-down menu.
  2. On the Manage Rapid Boards screen, click the Configure link corresponding to the Rapid Board of interest.
  3. On the Rapid Board Configuration screen, click the Quick Filters tab.
  4. In the Name field, enter Bugs only (or whatever is appropriate for your needs).
  5. In the JQL field, enter type = bug (or whatever is appropriate for your needs).
  6. Click the Add button, then click Use.
  7. Your Rapid Board will now have a new button for your new Quick Filter.

For more details, please see Configuring Quick Filters.

13. Displaying a Wallboard

A Wallboard displays vital data about project progress to anyone walking by.

  1. Ensure that the JIRA Wallboards Plugin has been installed. (This is similar to installing the GreenHopper plugin as described above.)
  2. Click the Dashboard menu in the top navigation bar and create a new JIRA dashboard for your new wallboard.
    (info) Since existing dashboards may contain gadgets which are not wallboard-compatible, avoid copying an existing dashboard.
  3. On your new dashboard, click the Add Gadget link (top right). The Gadgets Directory will display. Find the GreenHopper Wallboard Gadget in the list of gadgets and click Add it now.
  4. Add any other wallboard-compatible gadgets to your new dashboard.
    (tick)Tip: By default, all available gadgets are listed. However, many of these gadgets are not wallboard-compatible. To restrict the list of gadgets to wallboard-compatible ones only, select the Wallboard category at the left of the Gadgets Directory.
  5. Select View as Wallboard from the Tools drop-down on your 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 the page. Wallboards are optimised for 1920x1080 and 1920x1200 pixel resolution screens, but should also work in some other resolution modes.

For more information, please see the documentation on the GreenHopper gadgets, the Wallboards Plugin and the JIRA Dashboard.

Thank you for reading this guide.

Thanks for taking the time to try GreenHopper using this guide. To help continue your journey, our support staff are always ready to answer your questions in Atlassian Answers for GreenHopper, or solve specific problems at our support portal http://support.atlassian.com.

  • No labels



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.