nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How many projects support scrum insights?

PTO Noel Rubio

In my company we have 6 different development teams, 1 UX team and 1 Operations team. 5 of the development teams work on front-end issues and 1 just back-end issues.

We have 1 scrum board configured for each development team showing all the issues involved in their sprints. We have a filter for each board that shows:

- For the 5 full stack teams: issues from their own project + issues from UX team project
- For the back end team: issues from their own project

With that configuration board Insights worked like a charm in each one of the scrum boards.

Last week we decide to also include operation issue in the development sprints. Therefore we change the filter to show:
- For the 5 full stack teams: own project + UX project + Operations project
- For the back end team: own project + Operations project

With that change in the filter board Insights stop working in the 5 full stack scrums. A message like this appears:
Captura de Pantalla 2022-10-24 a las 16.46.03.png

Despite adding the same filter to the back end scrum board, their Insights are still visible.

I've already checked if it was a permissions problem but all 3 projects involved in the filters (every development project, UX team project and Operations project) are configured to give the right "View aggregated data" to any logged used.

So, my question is: is board insights limited to filters including 1 or 2 projects?
I did not find any information in the documentation about that. In fact, the error message suggests that insights should work only if you have 1 project configured, but it has been (and it is working for the back end team) with 2 projects configured, which is even more confusing.

Accepted answers

PTO Noel Rubio

At the end the problem was that some project references used in the ones that don't work were IDs instead of the project name, so I changed one filter from something like this:

project = 11142 OR 
project = 11143 AND "Development team" = "Team A" OR 
project = "Operations" AND "Development team" = "Team B" 
ORDER BY priority DESC

project = "Team A" OR 
project = "UX" AND "Development team" = "Team A" OR 
project = "Operations" AND "Development team" = "Team A" 
ORDER BY priority DESC

After changing that insights are working again :exploding-head: Maybe the problem was that the filter was combining IDs references with Name reference :S

All comments

Nic Brough -Adaptavist-

There's no limit to the number of projects, the problem is with the permissions your users have to see all the projects that the board might include, or that the board is a personal one, rather than one linked to a project.

PTO Noel Rubio

Hi @Nic Brough -Adaptavist-

Thanks for your answer, but this does not seem to be the problem. I myself (being and admin by the way) can browse all the projects individually. I also have "View aggregated data" permission (I even use the permission helper to check just in case) in all of them.

Let me paste a pseudo-code version of the JQL filter we use and what we changed. We initially have:

For full stack teams:

project = {development_project} OR 
project = {ux_project} AND "Development team" = {development_team} 
ORDER BY priority DESC

For back end team:

project = {development_project}
ORDER BY priority DESC

With that JQL filter Insights were working without any problem. As we also wanted to add Operations issues related to each development team, we include a new OR in the filter:

project = {operations_project} AND "Development team" = {development_team}

And the filters end up looking this way:

For full stack teams:

project = {development_project} OR 
project = {ux_project} AND "Development team" = {development_team} OR 
project = {operations_project} AND "Development team" = {development_team} 
ORDER BY priority DESC

For back end team:

project = {development_project}
project = {operations_project} AND "Development team" = {development_team} 
ORDER BY priority DESC

With these new filters the Insights feature is "blocked" in any full stack scrum boards (3 projects) for any user whereas it is still working (also for any user) in the back end scrum board (2 projects). That is what made me think that the problem is related with the number of projects.

Nic Brough -Adaptavist-

In the Jira systems I've used to (partially) replicate this, it works fine.

To be clear, I've used a client system which has a similar config (I'm an admin, but it's not my system, so I do not change anything without asking), and a test system (which I can mess with the setup, but doesn't really have enough data to play with)

But it does lead me to ask - what types of projects are you working with? Company or Team managed, and are they Jira Work Management, Product Discovery, Service Management or Software?

PTO Noel Rubio

That's the thing, everything should work and I think I found the problem this morning by just playing around with filters so I'm posting here my solution just in case it could help someone else.

I was playing around with the filters, when I realize that there was an extra different between the one that was working an the other. Some project references used in the ones that don't work were IDs instead of the project name, so I changed one filter from something like this:

project = 11142 OR 
project = 11143 AND "Development team" = "Team A" OR 
project = "Operations" AND "Development team" = "Team B" 
ORDER BY priority DESC

project = "Team A" OR 
project = "UX" AND "Development team" = "Team A" OR 
project = "Operations" AND "Development team" = "Team A" 
ORDER BY priority DESC

After changing that insights are working again :exploding-head: Maybe the problem was that the filter was combining IDs references with Name reference :S

By the way, all projects are Software company managed (I did forget to add that info)

PTO Noel Rubio

At the end the problem was that some project references used in the ones that don't work were IDs instead of the project name, so I changed one filter from something like this:

project = 11142 OR 
project = 11143 AND "Development team" = "Team A" OR 
project = "Operations" AND "Development team" = "Team B" 
ORDER BY priority DESC

project = "Team A" OR 
project = "UX" AND "Development team" = "Team A" OR 
project = "Operations" AND "Development team" = "Team A" 
ORDER BY priority DESC

After changing that insights are working again :exploding-head: Maybe the problem was that the filter was combining IDs references with Name reference :S

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud