You have noticed that for some Admin accounts (being in Symantec Administrator role) when running patch report - the results are 0.
While troubleshooting you have found that for those sub-reports - the parameter is being set which is unexpected and can not be modified within this report:

To Reproduce:
- Create a new User account and give this user Symantec Admin or Patch admin role.
- Create a Custom Severity value in Core Services for patch:

- Log in with this user account to console and open Compliance By Bulletin.
- Assign custom severity to a few random bulletins. In this sample, you have assigned NotCrit3 to NP++.
- Then open Windows Compliance by Computer, where you can specify the Custom Severity parameter, and set it to our custom value so the report would have filtered results:

- Then if you go into any sub-reports (drill-down) and select Applicable, or Not Installed, etc - the custom severity parameter is pre-configured (which seems to be expected - as it's also visible as configure-able).

- Yet then if you go into another report - Compliance By Bulletin (which does not have this custom severity parameter configurable):

- And select another bulletin without set custom severity:

- You would end up with 0 results since these parameters have filtered the expected results.