You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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:
Expected Test:
Add any information about how this will be tested.
The text was updated successfully, but these errors were encountered: