Hi Lynn_Jira,

5.8.7 is a very old release, we would recommend you upgrade to GreenHopper 5.10.x on JIRA 5.x.

Enabling the Scrum for Rapid Board labs option will enable the Sprint field for use in the Rapid Board, though the Scrum Rapid Board in 5.8.7 is fairly rudimentary.

Thanks,
Shaun

We are using GH 5.8.7, when open GreenHopper administration screens, the greenhopper labs displayed as below:
----------------------
GreenHopper Labs
GreenHopper Labs is a testing ground for experimental features that aren't quite ready for prime time.
They may change or disappear at any time. Details on what is currently being tested can be found here.
Features: Scrum for Rapid Board
Analytics - Allows GreenHopper to collect Rapid Board usage data. Enabling this helps us make the product better based on customer usage patterns.
----------------------
There isn't a option about Sprint field. Would you please provide more ifnormation about how to enable that and how to test?

I think JP means that he is looking for a demo instance.

JP: You can find that here:
https://jira.atlassian.com/secure/RapidStart.jspa

Hi JP,

You can go ahead and test it today The feature is enabled as a Lab option in GreenHopper 5.8.6 and above, just go the Labs section in the GreenHopper administration screens (or you will see an option to enable it on the Getting Started page if you are an admin).

Thanks
Shaun

Hi All,
We're pleased to note that the new Sprint field has actually been added in 5.8.6 and above with the introduction of Scrum for thr Rapid Board in labs. If you'd like to try it out and provide feedback while we continue to implement this new experience we invite you to enable the lab.
Thanks,
Shaun

.. and if you have any testable version somewhere, I would like to try it, please.

-JP

Hi,

We have following issue with Greenhopper.
1. We have timeboxed(2 weeks) sprints, like this

Unscheduled
Product Backlog
|
[-]-> Release 1 Backlog
|    |
|    |--> Sprint1
|    |
|    |--> Sprint2
|    |
|    |--> Sprint3
|    |
|    |--> Hardening Sprint4
|
[-]-> Release 2 Backlog
|    |
|    |--> Sprint1
|    |
|    |--> Sprint2
|
[+]-> Releases
...

2. Then we have those "Release Versions" where we would like to have Road Maps and Release Notes

Unscheduled
Product Backlog
|
[+]-> Release 1 Backlog
|
[+]-> Release 1 Backlog
|
[-]-> Releases
|    |
|    |--> 1.0.0.0
|    |
|    |--> 1.0.0.1
|    |
|    |--> 1.1.0.0
...

—

So, the issue is that..

1. when we plan Releases and create our Roadmap we drag&drop those issues to Releases and to Version like 1.0.0.0
   • this works fine and we can get those planned Roadmaps and early version releases from Fix Version/s field (NICE!)
2. when we start planning sprints, teams splits stories/features to sub-tasks, and they throw whole parent task to sprint
   • well.. now we lost that release and roadmap and early release notes
   • I understand, that we could throw only sub-tasks to sprint, but..
     • team wants to see parent tasks in sprint level(Planning board), because it is difficult to know which "implementation" sub-task is which
     • some of the tasks are so small, that we do not want to use time to split those to sub-tasks

So, any possibility to add

1. "Append Version" to Planning Board (e.g. CTRL button to Drag&Drop)?
2. "Append Version" to Bulk Change

Regs,
-JP

Hi Rob,

Yeah, you are kind of making the same point as i am.
Though i know it's not very 'Agile', our Product Owners do schedule a few sprints ahead. That's more or less part of the 'Capacity Management' / 'Milestone Planning' (can i get %amount% work done with %amount% of time)

@Shaun; multiple iterations would be great, but i suppose (just trying to think with you) having the ability to 'mark' multiple sprints (like you can do now with the next one) would suffice for us as well.
We would still have to 'overhaul' our current sprints and backlogs, but that's something we can cope with, i think.

Regards,

Edwin

Hi Shaun

The Rapid Board feature is great when Planning a single sprint (without using fixVersion), however I am pretty much making the same point as Edwin ( at least I think I am ). The fact that you can't use the new field to plan multiple iterations.
I haven't had much time to play with the rapid boards to be honest but I use the drag/drop functionality in the standard planning board quite a lot to schedule issues in future sprints. However it seems like I still have to use the fixVersion to do that.
Granted I can just drag every issue to a version that is an actual release and then (correct me if I am wrong) do macro planning using the rapid board, one sprint at a time. My main issues here are:

1. You cant use the sprint version on the standard Planning board
2. There is no correlation between existing sprints and the rapid board
3. I can only start one sprint and plan the next. Project management becomes extremely difficult here and there is a backwards step in the functionality as with the current planning board I can front load as many sprints as I like. the new rapid board makes the process much more reactive and puts project planning in danger as it forces the user to do last minute planning.

From your previous comment, the new sprint field is not available to the standard planning board so it will become clunky when trying to quickly get cards into a particular sprint.

Hope that is a better description of my questions.

Also as already mentioned, there is currently no easy way to move fix versions to sprint fields, and as neither are visible between rapid board and planning board, it makes each feature mutually exclusive and introduces another way to confuse how you are planning your sprints.

Hopefully I am not missing something fundamental here

Rob

Hi Edwin,

You're right that the current version only plans one sprint in advance but during a Sprint you can still use the Plan mode to rank stories and measure potential future Sprints by dragging the Sprint marker.

We're currently focusing on making this experience as slick as possible but Multiple Sprint planning will be something we tackle thereafter.

Thanks,
Shaun

Hi Rob,

I'm not sure what you mean, using the Scrum rapid board (which is in labs while we continue to enhance it and make it the best experience possible) you can plan a sprint using the new Sprint field (with no use of fixVersion).

The Scrum Rapid Boards are still missing quite a few features but we would appreciate any and all feedback while we continue to build them out. They are ready for basic Sprint planning now and we will greatly expand the capabilities over the next couple of months.

Thanks,
Shaun