Company-managed project board of multiple projects (combined) keeps "self" deleting

Charlie Zeier_41tmhf

i'm trying to create a board in company-managed Jira Enterprise that combines multiple project boards from the same space together. I created a filter yet the system 

Created board based on query of:

     (type = Story AND Sprint IS NOT EMPTY) ORDER BY assignee DESC

 

---

It appears to create the board

 

---

However, it doesn't "stick", almost as though it "self" deleted. It presents the above for a hot-minute and then I get the following

---

 

In looking at Jira community and documentation, it is possible. What I can't determine is why it is deleting itself. Do we have to account for parity in sprint names across the individual project/boards? 

Any thoughts on why this is happening? We have people assigned work across multiple boards within the same space and want to use one board during our stand-up meetings, etc.

Trudy P Claspill

Hello @Charlie Zeier 

Welcome to the Atlassian community.

Looking at your filter:

 (type = Story AND Sprint IS NOT EMPTY) ORDER BY assignee DESC

This filter does not constrain the Projects/Spaces to be included. When you do not explicitly constrain the spaces (by using criteria for the Project field) the filter will attempt to read data from absolutely every project/space (software, business, and service, team managed and company managed) in the Jira instance. If you don't have access to any one of those projects/spaces that can cause unexpected things to happen with your filter/board.

Can you try adding a project in (X, Y, Z) type of criteria to your filter to see if that resolves the issue?