Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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.



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
Ignacio Pulgar Community Leader Aug 14, 2019

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".


2. We have Global.


Ignacio Pulgar Community Leader Aug 14, 2019

Jira Software Server or Cloud?

If Server, what version?

Server v7.3.8.

Ignacio Pulgar Community Leader Aug 14, 2019

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.)

No, it's Standard issue type.


Ignacio Pulgar Community Leader Aug 15, 2019

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):

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...


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Apps & Integrations

Send an Email or Publish to Confluence - What should you do with your release notes?

Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...

246 views 1 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you