Patch Reports using not expected parameters for drill-down sub-reports
search cancel

Patch Reports using not expected parameters for drill-down sub-reports

book

Article ID: 397012

calendar_today

Updated On: 05-30-2025

Products

IT Management Suite Patch Management Solution

Issue/Introduction

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:

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



  3. Log in with this user account to console and open Compliance By Bulletin.
  4. Assign custom severity to a few random bulletins. In this sample, you have assigned NotCrit3 to NP++.
  5. 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:



  6. 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).



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



  8. And select another bulletin without set custom severity:

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

 

Environment

ITMS 8.7.3

Cause

Information is incorrectly filtered out in Patch report drill-downs for cloned Administrator accounts.

Resolution

This issue has been fixed with our ITMS 8.8 Release.

For those with ITMS 8.7.3 release, refer to the pointfix available under CUMULATIVE POST ITMS 8.7.3 POINT FIXES: