Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(severityNone): Implement Identification of Issue Matches of Severity None #378

Open
2 tasks
Tracked by #387
lolaapenna opened this issue Nov 15, 2024 · 2 comments
Open
2 tasks
Tracked by #387
Assignees

Comments

@lolaapenna
Copy link
Collaborator

Task Description
Currently issue matches with severity value none are aggregated with issue matches of all severity levels. We need to implement a segregation of those with severity value none so that they do not appear in as issues in the service detail view.

Acceptance Criteria:

  • Default filter selection for All Severities but None
  • Issues in the service detail view does not include those with severity None

Expected Test:
Add any information about how this will be tested.

@lolaapenna
Copy link
Collaborator Author

Changes will be implemented on the API first before UI.

@lolaapenna lolaapenna assigned MR2011 and unassigned drochow Nov 26, 2024
@hodanoori
Copy link

To prevent misleading users, componentInstanceCount and issueMatchCount for the Services view should be calculated separately for each severity level in the API. These counts will then be displayed with distinct icons in the corresponding count column on the Services main list view.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants