Just installed the Burndown Chart, but it looks like it only allows time spans of less that three months. I want to do a burn down for the entire project that is 1 year long.
Is that possible?
Hi @Kevin Harvey ,
You can do this with our Great Gadgets add-on (available for both Jira Server and Jira Cloud).
It offers a "Release Burndown Burnup" dashboard gadget that is based on a filter and allows ou to set the start/end date of the project.
More details about how to configure it can be found in the add-ons documentation: https://bitbucket.org/StonikByte/great-gadgets-add-on/wiki/Home#!release-burnup-burndown-chart
Danut.
Hi @Kevin Harvey,
Just interesting What is the purpose to see burndown on long time period?
How do you do it now after 2 years?
Thanks
Cheers,
Gonchik Tsymzhitov
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Our projects are 2+ years, but not agile or sprint based but waterfall. (Atlassian seems to assume sprint based).
So knowing that we have 600 man days of estimate over 2 years, is the rate at which we are burning down gong to get us to the end; that is what the purpose is.
And I found no automated solution. Each Monday I export all of the outstanding Jiras for each project into excel. Then convert the estimate (which is in minuets !??) into days. Then add that to a plot.
A real pain!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hm, what do you think about some Qlick View/ Tableau tools getting data from slave DB.
You will need to write once the request, then just updating data a delta info.
https://www.youtube.com/watch?v=DTp7nrcI6G0
What do you think?
Hope it helps
Cheers,
Gonchik Tsymzhitov
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply.
That assumes that we are using Scrum - we are not; Hence the need to do the burndown over a much longer timeframe. Indeed our projects often run for 2 years.
I will put a request in as suggested,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, Kevin!
Agile methodology recommends Sprints length 1 – 4 weeks. Most Scrum trainers and coaches recommend Sprints to be 1 or 2 weeks long: http://www.agileadvice.com/2014/06/12/howtoapplyagile/21-tips-on-choosing-a-sprint-length/ .
If you want any plugin customization, please send request to Artezio: http://www.artezio.com/press-room/send-request-online
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.