Index
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
4 April 2013
The Atlassian team announces the release of GreenHopper 6.1.6, bringing you:
This release also includes a number of fixes.
Upgrading to GreenHopper 6.1.6 is free for all customers with an active GreenHopper license.
If you are using GreenHopper "behind-the-firewall" (that is, if GreenHopper is installed on-premises at your site), you can upgrade GreenHopper via the JIRA Plugin Manager. Before upgrading, please read the GreenHopper 6.1.6 Upgrade Notes.
If you are using GreenHopper OnDemand, please watch the GreenHopper OnDemand Release Summary for the latest updates.
New gadget: Days Remaining in Sprint
This gadget shows how long you have before the current sprint ends. Great for team wallboards.
New gadget: Sprint Burndown
This much-requested gadget shows the actual and estimated amount of work to be done in a sprint:
You can choose to always automatically display the current sprint.
Create Versions in GreenHopper
For your convenience, versions can now be created directly from the Versions panel in Plan mode:
(It is intended that the Version Start Date will, in a near future release of GreenHopper, be used when calculating the Projected Release Date on the Version Report.)
Your administrator will need to activate Release Planning in GreenHopper Labs before you can create versions in GreenHopper.
View trend lines on the Version Report
The Version Report now shows trend lines, which help to illustrate the predicted release date:
Your administrator will need to activate Release Planning in GreenHopper Labs before you can view the Version Report.
Updates and Fixes in this release
GreenHopper 6.1.6 includes the following updates and bug fixes:
概要
コンテンツ ツール
アプリ
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.
12 Comments
Viðar Svansson [Tempo]
Apr 04, 2013Is the start date still a GreenHopper specific attribute on versions?
Rosie Jameson [Atlassian]
Apr 07, 2013Yes, this is currently a GreenHopper-specific field (not a built-in JIRA field). But we are planning to change this in the near future. Please watch upcoming releases.
Viðar Svansson [Tempo]
Apr 08, 2013Great news. Do you have an issue to watch for this?
Jamie
Apr 04, 2013Why do all the new GreenHopper gadgets add loads of padding underneath when viewed as Wallboard? Completely unusable at present as wallboard gadgets.
Tom Kotecki
Apr 08, 2013Hi ukjbrown,
This is a bug that we intend to fix really soon. You can follow it here: GHS-8319 - Getting issue details... STATUS
Cheers
Tom Kotecki
Product Manager, GreenHopper
Kim Poulsen
Apr 05, 2013I tried to comment on GHS-8023 but I am not sure it went through. So here's a quick recap:
Problem:
Lets assume we have a version where the first issues were added 1 year ago, then some more during time and then worked on a little and at last worked on a lot.
The curve will look somewhat like this (I cannot attach an image).
T = trend line; S=Total story points; W=Points completed:
Trend is way off even though work is complete!
So the trend line is going to be way off if it is calculated from a fixed start date designated to the very first issue that was added to the version. You seem to have that taken care of by adding a "start date" to a version. Well done. I think however that the fixed start date is both close to unusable for accelerating release-burns like this one and also too hard to use.
Of course I assume that most releases indeed are accelerating towards the end but my 14 years of project experience supports that assumption quite well.
Solution:
I suggest a moving trend calculating the trend based on some (configurable) period before the current date. In this case calculating the trend based on say the last month of burn will provide me with a massively better estimate of completion compared to the fixed date. Also I will have the estimate current without having to set new "start dates" etc.
Another suggestion is to kind of "keep the history" by saving the now piecewise linear trend fit so it can be shown or hidden to show how the trend converges on the possible release date scenarios. The pieces would follow for example calendar months or even better our sprints.
I hope this feedback is useful.
Rosie Jameson [Atlassian]
Apr 07, 2013We are planning to use the Version Start Date to inform the graph. Please stay tuned for upcoming releases.
davfive
Aug 02, 2013I totally agree with this. The trendline should be estimated based on the current velocity which is calculated as the average velocity over the past N sprints (N = 3 or 5 or something similar). It really doesn't matter what happened at the beginning of the release if it was a year ago, only what the recent data tells us.
Paudi Moriarty
Apr 05, 2013I'm seeing lots of padding underneath the new gadgets in wallboard mode too. Tested with Chrome on Linux and Firefox on Windows.
Tom Kotecki
Apr 08, 2013Paudi,
We will be fixing this shortly: GHS-8319 - Getting issue details... STATUS
BlueKai Support
Apr 08, 2013Am I missing how to display burndown charts as high contrast and full screen?
I can add Scrum boards to my dashboard, but its not really visually compelling with the nav bar and standard view...
Paudi Moriarty
Apr 10, 2013JIRA Wallboard plugin is what you want.