Repository navigation
In Vulnerabilities page, the Vulnerability view filter and Advanced filter do not connecting with each other #1226
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
The vulnerability view selection does not interact with the advanced filter's field.
The registry and infrastructure should not have namespaces and service/container
Expected Behavior
The vulnerability view filter should restrict the advanced filter.
If the vulnerability view is registry or infrastructure, in the advanced filter, the namespace should not be shown, and service and container should not appear from the dorpdown
Steps To Reproduce
No response
Environment
- OS:
- Architecture:Anything else?
No response
Activity
[-]In Vulnerabilities page, the Category filter and Advanced filter do not connecting with each other[/-][+]In Vulnerabilities page, the Vulnerability view filter and Advanced filter do not connecting with each other[/+]fix(neuvector#1226): In Vulnerabilities page, the Vulnerability view …
fix(neuvector#1226): In Vulnerabilities page, the Vulnerability view …
fix(#1226): In Vulnerabilities page, the Vulnerability view filter an…
rushk014 commentedon May 27, 2026
nv-build-manager#4319
selvamt94 commentedon Jun 10, 2026
Verified with manager build 5324, advance filter does not show namespace option for registry and infrastructure view.
advance-filter-vulnerabilities.webm