What is the best way to manage multiple projects (12) across 3 teams/backlogs?

[kevin yanders]

Hello!  I am a SM with some Jira experience but previously had an administrator who took care of setting up our environments.  I now have 3 teams working in 3 backlogs across approx. 12 projects for a large company.  We have members who do not like the current set up and would like to have better visibility into each project independently.  They suggested a separate board for each project but we all can agree that would be messy in many ways.  Looking for more potential ways to solve this dilemma than I currently have the Jira knowledge to do so with and have not found a thread on this particular topic.  Thanks!

[Filipe Santos]

I tried Nic's suggestions and none of them worked for me.

After some wandering around I realized one of our issue types had the Assignee field hidden in Field Configuration. When I changed it to not hidden, the JQL "assignee IS EMPTY" started showing the issues that were preventing me from disallowing unassigned issues

[Nic Brough -Adaptavist-]

That suggests you have project permissions or issue security that is stopping you from seeing the issue, or your index may be damaged in some way.  To work these out:

When you go to the main user list of projects off the main menu, count how many you can see there.  Then go to admin -> projects and see how many there are in there.  If the number is different, there are projects you can't see as a users, and your issue is probably lurking in there.

Go to admin -> issue security and check out the schemes - are there any that might be hiding an issue from you?

Try re-indexing

If it's none of those, your last resort is to look in the database - you need something like

select * from jiraissue where assignee = ""

to look for the empty assignee field.  You'll then need to have a look at why the index is failing to pick that up (because that's what the check is being done on)