Sprint insights burndown uses only one project

[Alex Hoogendoorn]

Hi,

We're using a sprint board which includes several projects. Each project can have stories with points on them.

When I look at the burdown in the insights of the active sprint it seems like only the points of stories in the main project are included, not the points on stories of all projects visible on the board.

Is this a feature or a bug that still needs to be fixed. I'd like to see the insights to be calculates over all issues in the active sprint.

Cheers

[Danut M [StonikByte]]

Hi @Alex Hoogendoorn,

How are the sprints? Do you have multiple sprints, like one sprint for each project? Or only one active sprint that includes all the issues from all projects? I think the burndown will work as you expect only if there is one sprint...

If you want a good cross-projects burndown chart, I would recommend trying our Great Gadgets app. It offers many gadgets for tracking projects, including a Release Burnup Burndown Chart gadget that allows you to generate the burndown at the release level.

Have a look over these articles from our blog, to make an idea about how many things you can track with this app and how:

• Cross-teams release burndown chart in Jira with Great Gadgets app 
• How to track multi-team or scaled-agile projects (such as SAFe®) in Jira with Great Gadgets app 

I hope this helps.

Danut. 

[Alex Hoogendoorn]

Hi Danut,

We have only one active sprint and it takes issues from multiple projects. The sprint, burnup and burndown reports generate correctly. It's just the burndown graph in the insights of the active sprint that seems to be missing issues (I know it's still in beta :-)).

Thanks

[Sanjog Sigdel]

Hi @Alex Hoogendoorn Welcome to the community.

Can you please share your jira filter query for your sprint board. Your Filter query for the sprint board determines what sprint reports you are generating.

In my case I've a scrum board which lists tickets from both Projects A and B. my filter query is like:

project in (A, B) ORDER BY Rank ASC

Then this is how my sprint report generated in Jira looks like:

[Alex Hoogendoorn]

Thanks Sanjog,

The query is quite large, and I guess it could be simplified, but that's another issue. The query was built before I joined the team. The query is:

project in (A, B, C, D) AND NOT (issuetype = Epic AND (status = Done OR status = Future OR status = Archived OR project = E)) ORDER BY Rank ASC

Also the Sprint report (and burndown and burnup reports) generate correctly. The issue is with the burndown graph in the insights of the active sprint only.

Thanks for your help.