Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All 0 values in burndown chart #4

Open
burdman33 opened this issue May 14, 2015 · 4 comments
Open

All 0 values in burndown chart #4

burdman33 opened this issue May 14, 2015 · 4 comments

Comments

@burdman33
Copy link

I have the jira-burndown widget up and running on my dashboard, but the graph is rendering lines with only y=0 values. I've checked the json be passed to the widget, and all y values being passed are equal to 0. I suspect the story point values aren't being calculated correctly in the job file, but I can't debug it. I'm wondering if you could help. The data I'm using is below.

JSON from REST API for my sprint:
{"changes":{"1425654885000":[{"key":"PR-1052","statC":{},"column":{"notDone":true,"newStatus":"1"}}],"1430405706000":[{"key":"PR-1335","column":{"notDone":true,"newStatus":"1"}}],"1430405882077":[{"key":"PR-1335","statC":{"newValue":3.0}}],"1430734042000":[{"key":"PR-1342","column":{"notDone":true,"newStatus":"1"}}],"1431338476447":[{"key":"PR-1335","added":true}],"1431338598587":[{"key":"PR-1342","added":true}],"1431340137813":[{"key":"PR-1342","statC":{"newValue":13.0}}],"1431423793000":[{"key":"PR-1335","column":{"notDone":false,"done":true,"newStatus":"6"}}],"1431423843000":[{"key":"PR-1335","column":{"notDone":true,"done":false,"newStatus":"3"}}],"1431433222000":[{"key":"PR-1335","column":{"notDone":false,"done":true,"newStatus":"5"}}],"1431447199837":[{"key":"PR-1052","statC":{"newValue":3.0}}],"1431447226807":[{"key":"PR-1052","added":true}],"1431451433000":[{"key":"PR-1373","statC":{},"column":{"notDone":true,"newStatus":"1"}}],"1431451439557":[{"key":"PR-1373","added":true}],"1431510563000":[{"key":"PR-1373","column":{"notDone":false,"done":true,"newStatus":"5"}}],"1431532201000":[{"key":"PR-1375","statC":{},"column":{"notDone":true,"newStatus":"1"}}],"1431532207317":[{"key":"PR-1375","added":true}],"1431605438000":[{"key":"PR-1376","statC":{},"column":{"notDone":true,"newStatus":"1"}}],"1431605464243":[{"key":"PR-1376","statC":{"newValue":1.0}}],"1431605477043":[{"key":"PR-1376","added":true}]},"startTime":1431340349088,"endTime":1431709200000,"now":1431623828922,"statisticField":{"typeId":"field","fieldId":"customfield_11042","id":"field_customfield_11042","name":"Story Points","isValid":true,"isEnabled":true,"renderer":"number"},"issueToParentKeys":{},"workRateData":{"timezone":"America/New_York","rates":[{"start":1431340349088,"end":1431709200000,"rate":1}]},"openCloseChanges":{}}

Object being passed from the scheduling to the widget (burndowns[tempSprintIndex]):
{"more-info"=>"30.0.3 Pricing Squad", :series=>[{:name=>"Target", :color=>"#959595", :data=>[{:x=>1431340349, :y=>0}, {:x=>1431709200, :y=>0}]}, {:name=>"Logged", :color=>"#10cd10", :data=>[{:x=>1431340349, :y=>0}, {:x=>1431637760, :y=>0}]}, {:name=>"Real", :color=>"#cd1010", :data=>[{:x=>1431340349, :y=>0}, {:x=>1431637760, :y=>0}]}]}

@funtastix
Copy link

I had the same problem. I figured out that the statistics in this widget are time based, not story point based. I removed the logged line (time logged doesn't exists for me), and changed (in the .rb file):

  • timeC -> statC
  • newEstimate -> newValue
  • oldEstimate -> oldValue

Then I changed the formatting on the y axis in the coffee script by removing the "/ 3600". Now it works great!

@burdman33
Copy link
Author

@funtastix Thanks for the suggestion. This almost worked. I am now getting y values, and the sprint start estimate is correct (i.e., starting number of story points). However, the burndown is not happening when a ticket status moves to complete. I suspect that the job is not checking for status changes and then subtracting the appropriate story points. I'm trying to wrap my head around the ruby in order to figure out where to add this. If you have any more suggestions, they would be appreciated!

@davelowelarsson
Copy link

@funtastix I seem to not get any "oldValue" in my rest calls to the api?

is there a magic command to get more data back?

@burdman33 did you resolve this ?

@vossim
Copy link
Owner

vossim commented Apr 12, 2016

@burdman33 @funtastix @SaltGurkan it looks like @Kavyahs created something that works for her. Unfortuntely she didn't add it as an option, so I cannot merge it. If anyone wants to add it as an option, feel free to create a PR.

PR from @Kavyahs as reference: #5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants