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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,456,881
Community Members
 
Community Events
176
Community Groups

eazyBI: Creating a Sprint Burndown that only looks at Story Points for Stories

My company has problems with the dev team putting Story Points on Sub Tasks. (Yes, I know it's a problem. Yes, we are trying to get them to stop.)

In the meantime, to clean up this reporting in our eazyBI dashboard, I am trying to make the burndown chart only show Story Points for Stories. However, when I essentially copy the included burndown functionality by creating new calculated members for Story Points such as:

([Measures].[Story Points resolved], [Issue Type].[Story]) as Story SP Resolved

to use in a copy of Cumulative Story Points Resolved, switching [Story Points resolved] for [Story SP Resolved]. I do this for [Story Points change], [Story Points history], [Cumulative Story Points resolved], and [Story Points remaining]. 

However, I keep getting very weird numbers. Am I just doing something dumb? Should these new calculated members take a filter?

 

Thanks!

1 answer

0 votes

@Alexander Stevens, I am sorry you have waited for an answer so long!

Your approach seems correct - putting the Issue Type in a tuple with measure should display this measure only for the specified issue type. 

Meanwhile, an even faster way would be to put the Issue Type on Page and select a filter to show the metrics only for Stories.

If you still experience problems, please contact us directly to support@eazybi.com with more details (screenshots, if possible) of why the numbers seem incorrect for you.

Lauma / support@eazybi.com

hi @Lauma Cīrule jumping in on this conversations, I am also currently making a sprint burndown specific to only subtask.

i have put the issue type on the page filter and run the table first but the coloumn "story points resolved" doesn't show any numbers, even tough in 20n march 2022, there are 4sp out of 17sp subtasks has been resolved. The table looks like this
Screen Shot 2022-03-25 at 15.31.29.png

as a result, the storypoints burndown for our subtask looks like this

Screen Shot 2022-03-25 at 15.29.25.png

i'm looking forward to hear back from you, thanks!

Hi @Qanitan Aryun ,

Just like in Jira, in eazyBI, sub-tasks follow their parent throughout Sprints. Are the four resolved Story points from sub-tasks whose parents are still in the same Sprint

For this reason, sub-tasks are not that reliable with the SP metric. In such cases, the Epic->Story relationship is a better option.

Best,

Roberts // support@eazybi.com

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events