[ 
https://issues.apache.org/jira/browse/RANGER-5880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dhaval Rajpara updated RANGER-5880:
-----------------------------------
    Description: 
Problem Statement
Currently, columns in several listing tables rendered in the Apache Ranger UI 
(such as Audit Listing and User Listing) cannot be resized. When fields like 
*User Name*  contain long text values, the text gets truncated or wraps 
awkwardly, making the page difficult to read and use.

Proposed Solution
Enable column resizing in Ranger UI listing tables—starting with *User Name*  
columns across all tables (along with any additional columns identified)—so 
users can adjust column widths to view long text clearly.

Steps to Reproduce
 # Log in to the Ranger Admin UI.
 # Navigate to *Audit* (Access Audits) or *Settings -> Users/Groups/Roles* 
(User Listing).
 # Observe records with long *User Name* Values and attempt to resize the 
column header.

Acceptance Criteria
 * Users can drag and resize *User Name* columns across Ranger UI listing 
tables (e.g., Audit Listing, User Listing).
 * Resizing a column adjusts its width smoothly without breaking table 
alignment, horizontal scrolling, or pagination controls.
 * Long text values become fully readable when the column width is expanded.

  was:
Problem Statement
Currently, columns in several listing tables rendered in the Apache Ranger UI 
(such as Audit Listing and User Listing) cannot be resized. When fields like 
*User Name*  contain long text values, the text gets truncated or wraps 
awkwardly, making the page difficult to read and use.

Proposed Solution
Enable column resizing in Ranger UI listing tables—starting with *User Name*  
columns across all tables (along with any additional columns identified)—so 
users can adjust column widths to view long text clearly.

Steps to Reproduce
# Log in to the Ranger Admin UI.
# Navigate to *Audit* (Access Audits) or *Settings -> Users/Groups/Roles* (User 
Listing).
# Observe records with long *User Name* Values and attempt to resize the column 
header.

Acceptance Criteria
* Users can drag and resize *User Name* columns across Ranger UI listing tables 
(e.g., Audit Listing, User Listing, Policy Listing, etc.).
* Resizing a column adjusts its width smoothly without breaking table 
alignment, horizontal scrolling, or pagination controls.
* Long text values become fully readable when the column width is expanded.


> Enable column resizing for  User Name columns across Ranger UI tables
> ---------------------------------------------------------------------
>
>                 Key: RANGER-5880
>                 URL: https://issues.apache.org/jira/browse/RANGER-5880
>             Project: Ranger
>          Issue Type: Improvement
>          Components: Ranger
>            Reporter: Dhaval Rajpara
>            Assignee: Dhaval Rajpara
>            Priority: Major
>
> Problem Statement
> Currently, columns in several listing tables rendered in the Apache Ranger UI 
> (such as Audit Listing and User Listing) cannot be resized. When fields like 
> *User Name*  contain long text values, the text gets truncated or wraps 
> awkwardly, making the page difficult to read and use.
> Proposed Solution
> Enable column resizing in Ranger UI listing tables—starting with *User Name*  
> columns across all tables (along with any additional columns identified)—so 
> users can adjust column widths to view long text clearly.
> Steps to Reproduce
>  # Log in to the Ranger Admin UI.
>  # Navigate to *Audit* (Access Audits) or *Settings -> Users/Groups/Roles* 
> (User Listing).
>  # Observe records with long *User Name* Values and attempt to resize the 
> column header.
> Acceptance Criteria
>  * Users can drag and resize *User Name* columns across Ranger UI listing 
> tables (e.g., Audit Listing, User Listing).
>  * Resizing a column adjusts its width smoothly without breaking table 
> alignment, horizontal scrolling, or pagination controls.
>  * Long text values become fully readable when the column width is expanded.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to