Skip to content

[TR] The search for risk profiles works inaccurately - #1671

Open
sofyakurilova wants to merge 1 commit into
devfrom
bug/risk_profile_filter
Open

sofyakurilova wants to merge 1 commit into
devfrom
bug/risk_profile_filter

Conversation

@sofyakurilova

Copy link
Copy Markdown
Collaborator

Fix risk profiles filtering

@sofyakurilova
sofyakurilova requested a review from hitnik October 23, 2026 06:36
@sofyakurilova sofyakurilova self-assigned this Oct 23, 2026
@sofyakurilova sofyakurilova added the ui Bug or request that impacts the user interface label Oct 23, 2026

@hitnik hitnik left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Testrun Pull Request Review: PR #1671

Summary of Changes

PR #1671 addresses an issue where searching for risk profiles in the list layout returned inaccurate results.

  • modules/ui/src/app/components/list-layout/list-layout.component.ts: Removed the risk attribute from the object returned by getObjectForFilter when this.title() === LayoutType.Profile. Profile filtering now operates exclusively on profile name and formatted created date (dd MMM yyyy), preventing search queries (such as "High") from inadvertently matching risk evaluation levels across unrelated profiles.
  • modules/ui/src/app/components/list-layout/list-layout.component.spec.ts: Added comprehensive unit test coverage under describe('when title is Profile') ensuring filtering operates on profile name and formatted date while ignoring risk and status fields.
  • docs/dev/mockoon.json: Updated mock profiles to align development mock data with test scenarios.

Assessment

  • Correctness & Functionality: Verified. The filter predicate matches the expected UX where users filter profiles by name and creation date without unexpected matches against profile risk metadata.
  • Test Coverage: Verified. New test specs explicitly test the exclusion of risk/status matches when searching by keyword.
  • Code Style & Quality: Clean, well-structured, and adheres to Angular signal/component conventions used across the project.

LGTM!

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ui Bug or request that impacts the user interface

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants