elastic/kibana

[Security Solution] Shared Exception List does not get refreshed after deleting previous search input

Fechada

#245.936 aberto em 10 de dez. de 2025

Ver no GitHubGuia do colaborador
 (6 comentários) (0 reação) (1 responsável)TypeScript (8.021 forks)batch import
Feature:Rule ExceptionsTeam: SecuritySolutionTeam:Detection EngineTeam:Detection EngineeringTeam:Detections and Respbugbug-fixereffort:lowgood first issueurgency:normalvalue:medium

Métricas do repositório

Stars
 (19.065 estrelas)
Métricas de merge de PR
 (Métricas PR pendentes)

Description

Describe the bug:

After doing a search on Shared Exception Lis, deleting the search term and clicking 'Refresh" button, the list does not get refreshed. The action is just complete if the user uses the delete button 'X' in the search bar.

https://github.com/user-attachments/assets/859bcc24-2ab8-4fe8-adc5-faf0babb61e5

Kibana/Elasticsearch Stack version:

9.3

Functional Area (e.g. Endpoint management, timelines, resolver, etc.):

Shared Exception List

Steps to reproduce:

  1. Have a list of Shared Exception Lists
  2. On search bar, search for a term that returns a result
  3. Delete (backspace) the term entered
  4. Click 'Refresh'

Current behavior:

The list does not get refreshed. The action is just complete if the user uses the delete button 'X' in the search bar.

Expected behavior:

The list should be refreshed.

Guia do colaborador

Direção de pesquisa
Investigate the Shared Exception List component in the Security Solution plugin (likely in x pack/plugins/security solution). Focus on the search bar and refresh button interaction. Determine why deleting the search term manually (via backspace) does not trigger a refresh, while the 'X' button does. Look at the component's state and the refresh function's dependencies. Consider if a useEffect or callback is missing the manual delete case. Check if there are any existing tests for this behavior.
Pilha de tecnologia
typescriptreact
Domain
frontend
Tipo Issue
Bug
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
3
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-3 horas
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
Bloqueado
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
Claro
Prerequisites
ReactTypeScriptKibana Security Solution
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
40