This question is about the "Version Report" in Greenhopper...
My goal in using the Version Report is to produce a report that looks similar to this: https://confluence.atlassian.com/download/attachments/323390967/gh_6-1-6_version-report.png?version=1&modificationDate=1365382810268&api=v2 (source: https://confluence.atlassian.com/display/GH/Viewing+the+Version+Report).
Up until recently the Version Report in our project is blank because the Sprint Team has not been using the "Fix Version" field on their Stories.
Recently I went in and updated the Fix Version value on all of the Stories our Sprint Team has completed, and on the Stories that are currently being worked-on in their current Sprint. I did this by going to the Sprint Report for each Sprint, opening the list of completed issues in Issue Navigator, and bulk editing those issues to apply the appropriate Fix Version to each issue.
The problem I'm running into our Version Report now looks like this: https://picasaweb.google.com/lh/photo/gZJBXkFECr___b8BkYfhsy7Co6soxMhSDgd1l8eKxLY.
As you can see, the X-Axis of our Version Report is in hours:minutes. The X-Axis values of the points on the Version Report are the days/times that I did the bulk edits to assign the appropriate Fix Version values, rather than the days/times that each Story was actually marked "Complete" by the developer or Sprint Team leader.
This seems like a bug in Greenhopper because it doesn't make sense to use an X-Axis value equal to the day/time that the Fix Version value was applied to the Story. Instead it should use an X-Axis value equal to the day/time that the Story was marked Complete.
Am I looking at this correct? Or am I doing something wrong here?
If this is a bug, below is the bug description that I plan to file on jira.atlassian.com.
Steps to reproduce:
1) Start with a JIRA instance that has an Agile Scrum project which was used by a Sprint Team that did not use the "Fix Version" field during their first 7 Sprints
2) Use the Issue Navigator to bulk edit the Stories in Sprints 0-4 to "Fix Version" M1
3) Use the Issue Navigator to bulk edit the Stories in Sprints 5-7 to "Fix Version" M2
4) Look at the "Version Reports" for M1 and M2
Expected Results: Version Reports for M1 and M2 would show a progression of Stories being completed over time culminating in milestones M1 and M2 respectively. This would mean that the X-Axis would be the day/time that the Stories were marked as complete.
Observable Results: Version Report uses and X-Axis value equal to the day/time that Steps 2 & 3 were completed. This is an example: https://picasaweb.google.com/lh/photo/gZJBXkFECr___b8BkYfhsy7Co6soxMhSDgd1l8eKxLY. The report is not usable this way.
The link to your picture isn't working for me, but from the description I believe that what you're seeing is how the chart is supposed to work.
It doesn't chart the progress of issues before they were added to the fix version, it's designed to show the changes in scope over time. It will show an increase in scope (and completed work, if the story is already complete when it's added) at the point when the fix version is set for the story.
You can change the point at which the graph starts though, by setting a start date on your fix version in the left hand panel listing the versions in Plan Mode on GreenHopper.
I've looked at all of the documentation about the Version Report and don't see anything that explains this. I'd like to better understand the reasoning behind this choice. It seems more intuitive to me for the chart to use an X-Axis of "Completion Date" rather than "Date Item Was Added to a Version". Would you mind either pointing me to some documentation that explains this, or providing more insight on why the Version Report works the way it does?
I think the photo links weren't working for you because Atlassian Answers added a "." at the end of the link (I definitely did not put the "." there), so here's another try without the "."...
The chart I want to create: https://confluence.atlassian.com/download/attachments/323390967/gh_6-1-6_version-report.png
Thanks for the link, I can see your chart now.
The X-Axis is intended to track the state of the Version at any given point in time, so that you can see how the scope changes, and how you are progressing towards completion.
The grey box is the total scope at that time, and the blue is the total completed scope. Before the point where you added your issues to it, the version had 0 points in scope.
The documentation is here: https://confluence.atlassian.com/display/GH/Viewing+the+Version+Report
I agree with you though, it doesn't really explain this, I will try to follow up so that it can be improved.
It sounds as though what you're looking for is a graph to chart progress of all the issues currently assigned to a Version, regardless when they got added, is that right?
Hi awesome community! In this article, I would like to describe the one of the toolset (service) for the analyze some problems on different Java-based instances, of course, as Atlassian admini...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs