Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Creating Jira reports via SQL

Tc I'm New Here Sep 06, 2022

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.

1 answer

0 votes

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.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events