Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HA synchronization button & status #8301

Open
2 tasks done
toxic0berliner opened this issue Feb 9, 2025 · 1 comment
Open
2 tasks done

HA synchronization button & status #8301

toxic0berliner opened this issue Feb 9, 2025 · 1 comment

Comments

@toxic0berliner
Copy link

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Is your feature request related to a problem? Please describe.

The nex 25.X UI for synchronization of opnSense nodes in High Availability section is problematic in 3 ways :

  • the button is labeled "restart services", no real mention of sync.
  • there is no feedback to indicate sucess
  • it's at the very bottom of the page

It was already descibed in issue #8292 but flagged as incomplete so since @EHRETic might not want to recreate his issue to follow the template, here I go....

Describe the solution you like

I would like the action button to be labeled with sync as sync is what users want to do when clicking it, restarting the services is a byproduct and I believe only done if sync changed anything.
I would also like the checkmark to come back once sync is completed instead of the current full-page reload.
Ideally this would also be much closer to the top of the page, probably in it's own section.

Describe alternatives you considered

live with it.

Additional context

I can understand maybe things are being transformed under the hood that might necessitate time to bring back full feature parity, but I do believe the clear labeling and feedback are necessary and merit to have an open issue until resolved or at least make sure they are not forgotten.

@AdSchellevis
Copy link
Member

I don't mind changing the tooltips (769fa74), but the workflow is what it is and in line with other components. By pushing the action to the backend it should also be slightly faster as requests don't have to circle back to the user browser.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants