Most Projects are not visible for me in our Production instance

[Joseph Warner]

I am able to view 504 projects (pm_project) in List View in my company's Dev, Test, and UAT instances. However, in Production I can only view 5 projects. I had another user confirm that there are 504 projects in Production and that he can view these projects with no problem. The only difference I can think of is that he has admin and security_admin roles in Production, which shouldn't matter. I have compared the read ACLs on the pm_project table and my roles in the environments and can't figure out what could be causing this.

UAT environment (504 projects)

Production environment (5 projects)

Here are my project-related roles in Production

I also have itil, and over 30 admin-related roles. I do not have the admin or security_admin role.

Has anyone experienced this before or can offer suggestions?

[Marco0o1]

Hi @Joseph Warner ,

I think you can have one of two problem:

1- The first I think if maybe you have acces to read the records from the "pm_project" table but you dont have acces to the other related tables like "customer_project" table, that can be de case and i can see because you censored the number but maybe you have a ACL that prevent to look for the CSPRxxxxx records but you can see for example the PRJ00xxxx records. You can tried to check.

2- Maybe you dont havve the correct roles, configured in the ACL, remember if your other account have the admin role and the ACL have tagged  the "Admin overrides" that user can look the record. I checked in my instance and you can missing a role like "sn_ppm_read,project_user, sn_customerservice.projectstakeholder or sn_customerservice.projectmanager" you need to check correctly the user really have the necessary roles.

Hope that help you. 

[Joseph Warner · Accepted solution]

Solution: provide admin role.

We gave up on identifying a root cause for this issue. My manager provided me with the admin role in our Production environment and it solved my issue and I was then able to see all 504 projects.

As stated above, by reviewing the applicable ACLs, the admin role should not be necessary to view projects, but it was the only thing that worked. No idea why having the admin role is necessary for me to view these project.

[Ray Gellenbeck]

1.  Check permissions on groups

2.  Check group membership (you did not post this).  You might have all the roles in the world, but if a story or project is assigned to a sprint or other organizational object that your group is not associated with, you won't see it.

99 times out of 100, the issue is a group that did not migrate and/or membership did not migrate.