Reports (burn-down and velocity) stopped working since May update

[Lisa McNab]

Hi,

In the last update, my burndown and velocity charts have stopped working.  For example, my previous 2 sprints had expected velocity and burndowns over the course of the sprint but since the upgrade, these have changed and are just showing a straight line.

My board\burn-down is a mixture of next gen and classic projects.  This wasn't causing any problems for reporting until the last update.

[Bogdan Gorka]

It is hard to help here withouth knowing more details or screenshots. If I were you, I would be looking for an error in source data using JQL search. Sprint reporting is based on the same data  as filters which can be reviewed via search functionality. For example, try searching for open and closed issues in a current sprint (using the sprint name) and see if you have any results. Check if you have issues in a Sprint that has started, sometimes people forget to start the Sprint and look for issues assigned to it. Just guessing....

project = ABC AND Sprint =

[Lisa McNab]

Hi,

I've attached some info.  You can see that there are story points and the work item is done but the #story points is not appearing on the sprint report.  The filter isn't showing any errors either.  When I view the filter query, I can see all the story points in the story point column. 

[Bogdan Gorka]

Hi @Lisa McNab 

I managed to reproduce your configuration and I won't be too much helpful here I'm afraid. It may be a bug or it is supposed to work this way.

Screen 1 - Story points are not visible in backlog if you use the Sprint Report (which is available only in the classic Jira Scrum project) to display also the NextGen project issues

Screen 2 - story points from the NextGen project are not visible when the JQL in a Scrum Board filter mixes issues from two types of projects

Screen 3 - story points from a NextGen project tasks are also not visible in Backlog

If there were project settings available in the NextGen project, I would check the permissions scheme for Scheduling and Sprint management, which is normally responsible for problems with story points and starting Sprints. But in the NextGen type of project, there are no permission settings like in a Classic. It looks like you are for some reason we are not supposed to mix issues from two types of projects

Hope it helps.

[Lisa McNab]

Hi,

Thanks for the suggested answer, is that using portfolio?

[Bogdan Gorka]

Could you please rephrase your question 'using portfolio'? I do not know what you mean.

[Lisa McNab]

The scheduling and sprint management seems to be part of the portfolio addin\plug-in\tool.

[Bogdan Gorka]

Sprint management is part of Jira Software. No plugins are required. Read more here: https://confluence.atlassian.com/jirasoftwareserver/running-sprints-in-a-scrum-project-938845426.html