elastic/kibana

[Security Solution] [Bug] Pagination visible on empty Shared Exception Lists page

Closed

#263296 opened on Apr 15, 2026

View on GitHub
 (6 comments) (0 reactions) (0 assignees)TypeScript (19,065 stars) (8,021 forks)batch import
Team: SecuritySolutionTeam:Detection EngineTeam:Detections and Respbugbug-fixergood first issueimpact:lowv9.4.0

Description

Describe the bug:

  • The Shared Exception Lists page displays pagination controls at the bottom of the table even when no exception lists exist. Per standard UI/UX patterns in Kibana/Elastic, pagination should typically be hidden or disabled when a "No items found" empty state is active.
  • Error Note: A "Bad Request" error toast also appears in the bottom right, which may be related to the underlying API call failing to fetch the list.

Kibana/Elasticsearch Stack version:

VERSION: 9.4.0 BC1
BUILD: 100832
COMMIT: 1735d6a99d4251d7dc4042f4523d3772493da3c4

Pre-conditions: 1.Kibana 9.4.0 must be running.

Steps to reproduce:

  1. Navigate to the Security app.
  2. In the left navigation menu, under Rules, select Shared exception lists.
  3. Ensure there are no shared exception lists currently created.
  4. Observe the bottom left/center of the content area.

Current behavior: The pagination bar is visible at the bottom of the page despite the "No exception lists found" empty state being displayed.

Expected behavior: The pagination footer (Rows per page, page navigation) should not be visible when the list is empty to reduce UI clutter and prevent user confusion.

ScreenCast (if relevant):

https://github.com/user-attachments/assets/8d42deab-3f0a-4364-8de4-e7d37e604334

Contributor guide