I want to create a burnup chart with SQL that uses the velocity from X previous sprints to estimate how much work will be done in the current sprint.
I have hacked together code to replicate the burndown chart and velocity chart.
For the burndown chart, I broke the task into different CTEs representing story points committed, added, reopened, removed, resolved, revised.
Just curious if anyone else is doing something similar and how far you've gotten.
No, you should not be trying this. A burnup chart is not a burnup if it has all of these things, and SQL is by far the worst way you can possibly report on Jira data. I don't need to see the SQL you've written to do this to be able to tell you that it's a) horrible, b) non-performant and c) almost certainly wrong.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.