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

Background

The Rapid Board is a fresh start for GreenHopper. We are building it to take advantage of the latest in web technology and provide you, the customer, with an awesome experience for planning, tracking and reporting on the progress of your agile projects and teams.
 
One thing is absolutely clear: your agile project does not necessarily map to a single JIRA Project. For that reason we have addressed the most common feature request — GHS-1800, support for more than one JIRA project in GreenHopper. Not being folks to sit still, we are taking this opportunity to introduce a new user experience with fewer page reloads and more useful URLs —  users will be able to have a URL for the displayed page (GHS-990).
 
The Rapid Board removes the complexity of the existing user interface (projects, contexts, boards, filters, versions, etc) while retaining the flexibility of GreenHopper. In fact, with the Rapid Board, GreenHopper is now a whole lot more flexible due to our use of the JIRA Query Language.
 
Further, the Rapid Board will return the Fix Version field back to its intended use-case, showing which versions a bug or story can be found in. The Rapid Board will result in a decoupling of Sprints from the Fix Version field (GHS-945).
 
We also have a new ranking field, Global Rank, which provides better performance than the previous solution. For the first time, you will be able to rank issues across JIRA Projects.
 
With the introduction of the Global Rank, JIRA and GreenHopper will no longer need to reindex all of the issues in each JIRA Project every evening (GHS-2727).

The Plan

The Rapid Board graduated from Labs in GreenHopper 5.8, initially providing support for Kanban teams. Scrum functionality was then introduced in GreenHopper 5.8.5 (in Labs). This initial implementation allows Scrum teams to use the Rapid Board to plan one sprint ahead, and we are focusing our development efforts on expanding your planning options. Our intention is to provide a very fast and easy approach to building a backlog, grooming the backlog then executing Sprints. We will continue to seek feedback from new adopters as we develop the functionality. 

In GreenHopper 6.0 we plan to push the existing boards (Planning, Task, Chart and Released Boards) to a Classic Mode and drop the "Rapid" title. The existing functionality on the Planning, Task, Chart and Released Boards will continue to be available for a number of releases until it becomes clear that the majority of customers have switched over. 

What now?

If you are a Kanban team we encourage you to switch to the Rapid Board today.

If you are a Scrum team there is no need to switch today, although we do invite you to try the new Plan tab on the Rapid Board (see Labs) and provide feedback. The Plan tab is where you scrub your backlog: review, estimate, and prioritise your stories and bugs, and where you create and plan iterations. If you are a Scrum team that requires planning across multiple JIRA projects, you will get value from the Rapid Board immediately.

A few pointers:

  • We'll support multiple iterations in a later release, but currently you can only have one iteration active (on the Work tab), and one in planning (on the Plan tab), per Rapid View.
  • You will not have a burndown chart on the Rapid Board Reports today; consider using the Agile Gadget temporarily.
  • Contexts are replaced by Rapid Views; there is no migration path today so if you are already using GreenHopper then you will need to recreate these from scratch.
  • 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.