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,463,945
Community Members
 
Community Events
176
Community Groups

Burndown chart report - sprint start don't include all issues types

Hi everyone,

We have a problem with burndown chart report.

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

When we start sprint, these issues types (Bug) 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".

We have others customized issues types that appear in the "start sprint" event.

 

Thanks,

3 answers

I have in the same sprint, 1 issue (New Bug) that was considered into "Sprint Start" event and other issue (New Bug) that wasn't considered isto "Sprint Start". Both issues were estimated before sprint start.

0 votes

Hi Júnior,

A couple of questions:

  1. Is the burndown chart set to be based in Story Points?
  2. If so, is the Story Points field mapped to the Bug issue type through a context?

Thanks and regards.

Hi @Ignacio Pulgar ,

1. Yes, the board is configured with "Story Points".

image.png

2. We have Global.

image.png

Jira Software Server or Cloud?

If Server, what version?

Server v7.3.8.

Is your custom Bug issuetype of subtask sub-type? If so, that's the cause.

Story Points on subtasks are not included in the Burndown Chart. (Only Story Points on parent tasks are included.)

https://confluence.atlassian.com/jirasoftwarecloud/burndown-chart-777002653.html

No, it's Standard issue type.

image.png

Oh, I see! I was about to suggest contacting Atlassian Support, but fortunately anyone else already did (I'll paste the known issue here just for other users convenience):

https://jira.atlassian.com/plugins/servlet/mobile#issue/JSWSERVER-13996

The bug occurs on issue creation, just with issues which automatically transitiion to a diferent status from the initial one as soon as created.

As you mentioned that it happened just with some issuetypes, I guess in your case the automatic transition is performed by a post-function on the Created transition of the workflow(s) set to be used by those issuetypes.

Of course, removing that automation would prevent this issue from happening again. May you possibly describe in detail the need that is covered by said automatic transition? Maybe we can find a different way for meeting your requirements that don't need to transition on isdue creation...

Regards.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events