Scrum reports based on saved filter

[Yi Meng]

Hi Community,

I have a team-managed scrum project. Teams are working on sprints in this project. Since there are several different teams, the PM wants to see the velocity report for individual team. Teams field is added in stories. And I create a filter to filter issues based on teams.

The JQL is 'Project = ABC and team= 'Team A'.

And I create a new scrum board based on this filter. Because it's a team-managed project, I have to put the new board in another company-managed scrum project. The board is created and all issues are listed on the board. But the reports shows nothing although all the information such as sprint are included in the board.

Is it because the original project is a team-managed project or I made something wrong? Thanks.

[Vasyl Krokha _Broken Build_]

Hi, @Yi Meng

Jira has a lot of limitations when it comes to tracking in multi-team environments, especially when your teams have slightly different setups. That's why we created two reporting apps:

1. Agile Reports and Gadgets - for scaled enterprises (Scrum, Kanban, SAFe, Less, SoS).
2. Agile Velocity Chart - for smaller companies with only Scrum teams.

Both apps allow you to track Sprint Metrics of several Scrum teams, with some having different estimation fields.

You can add multiple Scrum boards into the Team/Cross-team Velocity Chart for Scrum boards and select for some of them a custom estimation field comparing to the general configuration:

So that you don't need to create any additional boards and create a custom estimation field for the company-managed projects.

On top of that, you can see more Sprint Metrics than only Velocity, broken down by teams:

Even more, if you want to track Health of different teams on one chart, you can utilize a Benchmarking chart, where teams are presented as different bars on one chart:

Hope, you will find this answer useful!

Olexiy

[Trudy Claspill]

Hello @Yi Meng 

Team Managed projects use the Story point estimate field for story points. The Velocity report built into the Team Managed project is based on that.

Boards that are constructed from Company Managed projects or from saved filters are leverage the Story Points field, and the Velocity report for such boards is looking for data in that field.

That field has no data for Team Managed projects, so your Velocity report has not data upon which to report.

[Yi Meng]

And I can't even add story points field to team-managed project. If I can do it, I can at least copy the story point estimate field to story points field....

[Trudy Claspill]

I have no insight into why Atlassian chose to use different fields for Story Points in the two types of projects.

And yes, it appears that the Story Points field can't be added to Team Managed project issues. We should be able to add any field that has a Global Context. I made sure that in my system the field did have a global context, but still was not able to add it to a Team Managed project. It may be that a re-index needs to be completed first since I changed the custom field.

You might want to look for a third party app that enables you to do more sophisticated reporting. There may be one that would enable you to get the Velocity reports per team without moving the issues to a Company Managed project.

[Danut M _StonikByte_]

Hi @Yi Meng,

Have a look over this article:

https://community.atlassian.com/t5/App-Central/How-to-track-scaled-agile-SAFe-projects-in-Jira-with-Great/ba-p/1929694

As you can see, by using the Great Gadgets app you can easily track the teams in an environment similar to yours. The article describes a potential approach to follow.

Specifically for your case, you could use the Kanban Velocity / Throughput gadget, which uses a filter or JQL as input. This gadget does not use sprints, but uses time intervals - so you will need to align the time intervals with your sprints start/end dates.

Similar to this, you can have burndown / burnup charts at the team level or at the global cross-team / release level. These gadgets work with any type of estimate, can include sub-tasks in the calculation.

Find more about this gadget in these articles:

• https://community.atlassian.com/t5/App-Central/8-gadgets-for-a-powerful-Scrum-dashboard-in-Jira/ba-p/1683063
• https://community.atlassian.com/t5/Jira-articles/Building-a-powerful-Kanban-dashboard-in-Jira-with-Great-Gadgets/ba-p/1664331

You can start with 1-month free trial. If you have any questions, feel free to contact us at support@stonikbyte.com.

Hope this helps.

Danut

[Yi Meng]

Thanks @Trudy Claspill  That makes sense. 

But why Atlassian wants to use 2 different fields for the same purpose? This is weird. 

If I really need to create a new Scrum board to get reports based on teams, I have to move all of them to a new company-managed project and copy the value of story point estimated to story point field so that I can have the reports. 

Do you have any other suggestions? Thanks.