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.
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.)
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...
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
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