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,467,937
Community Members
 
Community Events
177
Community Groups

Does every issue type are considered on a burndown chart ?

Hi everyone,

I have a issue with my Burndown chart in my project, indeed the issue types - "Bug" and are not considered as burdowned when the status is Done. 

Same behavior when I looked to "sprint report" dashboard, those issues are in status "In progress" even if they are Done. I am quite lost, and I can't report to my management the velocity of my team. 

I add that for issue types "story" and "technical story" the burndown is working fine. 

 

Could you please help me to identifie a solution  

Thanks

Romain

5 answers

1 accepted

0 votes
Answer accepted

So I double checked the post- functions as noticed by Nic, and it appears that a the update history line was missing in my customized workflow. By addind this line the problem is solved.

Thanks evryone for your help.

Cheers

Romain

Hi everyone,

We have a similar problem.

We have a customized issueType called "Bug" with a customized workflow, screens, etc.

When we start sprint, these issues types didn't appear on the first row of table in the "Burndown chart" report.

I checked the workflow and i saw the post-function there "Update change history for an issue and store the issue in the database".

@Romain Paradan where you added this post function?

0 votes

So, there is something wrong with the workflow, because the status of the issues does not change when you transition.

You'll need to look at the workflow and probably the logs to work out why this is failing

I change the status with the status buton- No particular  or customised post-functions or transitions...

Thanks

I made some tests by modifying the status of the bugs it seems that it never goes to Done on the history tab. 

When I change it status to In progress I can see on the history 

DONE --> IN PROGRESS

 

When I change IN PROCESS to DONE nothing change on the history tab.. No other line added

If there's nothing in the history, that implies the status did not change, or if it did, it went through a broken process to get there.

How are you changing the status here?  Does the transition have any customised post-functions?

0 votes

On the board for the project, are Bugs you expect to be burning down in the far right hand column?

Thanks for your reply,

yes I think so...I can see Bugs on my board when they are Done in the right hand column. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events