Bug 2066207

Summary:	The new created policy should be always shown up on the first line
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	yahliu
Component:	Console	Assignee:	Kevin Cormier <kcormier>
Status:	CLOSED ERRATA	QA Contact:	Xiang Yin <xiyin>
Severity:	medium	Docs Contact:	Christopher Dawson <cdawson>
Priority:	unspecified
Version:	rhacm-2.5	CC:	dho
Target Milestone:	---	Flags:	bot-tracker-sync: rhacm-2.5+
Target Release:	rhacm-2.5
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-09 02:09:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 bot-tracker-sync 2022-03-29 16:08:48 UTC

G2Bsync 1081956158 comment 
 jamestalton Tue, 29 Mar 2022 14:39:39 UTC 
 G2Bsync
Tables save/restore the last sort state the user selected.
This is so that the user can control the table sorting and it is a consistent experience.

Create should take the user to the detail view for the item upon submit.
Edit should take the user to with the table view or the details view based on where the user initiated the edit action.

This should be consistent across ACM. It may not have been so in the past, but we need to standardize on consistency.

Comment 2 yahliu 2022-04-13 05:57:30 UTC

Verified on 2.5.0-DOWNSTREAM-2022-04-09-18-58-25. Design changed.

Comment 5 errata-xmlrpc 2022-06-09 02:09:49 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Red Hat Advanced Cluster Management 2.5 security updates, images, and bug fixes), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:4956

Comment 6 Ketrina Foster 2023-01-31 08:52:01 UTC Comment hidden (spam)

To ensure that a newly created policy always appears at the top of the list, you need to implement a sorting algorithm. The specific sorting algorithm will depend on the programming language and data structure you are using to store the policies.

Here is an example of how you can achieve this in JavaScript using an array:

javascript
Copy code
let policies = [];

function addPolicy(policy) {
  policies.unshift(policy);
}

function getPolicies() {
  return policies;
}
In this example, the addPolicy function adds the new policy to the beginning of the array using the unshift method. This way, the latest policy will always appear at the top when the policies are displayed using the getPolicies function.


https://www.landstaronline.me/

Comment 7 Aimee Bryant 2023-02-14 09:43:07 UTC Comment hidden (spam)

Thank you for sharing the information.


https://www.myhtspace.org/

Comment 8 m.arcusnguyeny75258 2023-04-24 06:09:54 UTC Comment hidden (spam)

You can verify the cluster status on any node using System > Clustering > Cluster Status page. The list displays each node in the cluster along with its status.
 https://www.mybalancenow.page/

Comment 9 Red Hat Bugzilla 2023-09-18 04:33:55 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days