elastic/kibana

[Fleet]: `Clear filters` option gets displayed itself everytime on navigating to Fleet>Agents tab.

Open

#154121 opened on Mar 31, 2023

View on GitHub
 (5 comments) (0 reactions) (0 assignees)TypeScript (19,065 stars) (8,021 forks)batch import
Team:Fleetbuggood first issueimpact:low

Description

Kibana version: 8.8 Snapshot kibana cloud environment

Host OS and Browser version: All, All

Build details:

VERSION: 8.8 Snapshot
BUILD: 61903
COMMIT: 5437cdab577d7868e5c353c44a10d399a513c22f

Preconditions:

  1. 8.8 Snapshot kibana cloud environment should be available.

Steps to reproduce:

  1. Navigate to Fleet>Agents tab.
  2. Observe Clear filters option gets displayed itself, without applying any additional filters other than default filters.

Screen Recording:

https://user-images.githubusercontent.com/77374876/229026994-1b0c920f-456d-4297-a7d2-3914599add0f.mp4

Expected Result: Clear filters option should not be displayed itself without applying any filters on navigating to Fleet>Agents tab.

Contributor guide

Tech stack
typescriptreact
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
ReactKibana development setup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The issue is a UI bug where the 'Clear filters' button appears without any applied filters in the Fleet > Agents tab. To fix, investigate the filter state management in the Agents page component. Look for logic that determines when to show the 'Clear filters' button, likely in the filter bar component. The bug may be due to default filters being applied incorrectly or a state initialization issue. Review recent commits or related PRs for context. The fix should ensure the button only shows when filters have been explicitly added by the user.