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

It seems like some "BlueOS vs Cockpit" conflicts could be resolved automatically #1628

Open
rafaellehmkuhl opened this issue Jan 28, 2025 · 0 comments
Assignees
Labels
ux Has to do with the user experience

Comments

@rafaellehmkuhl
Copy link
Member

Maybe we can use timestamps synced between Cockpit and BlueOS to solve the resolution without having the user to decide.

Probably, if we make sure the change was made by the user while not connected to BlueOS, and the same user was the last to change those settings, we can keep the Cockpit settings.

Or maybe we can allow the user to select an option to always select one or another, automatically.

@rafaellehmkuhl rafaellehmkuhl added the ux Has to do with the user experience label Jan 28, 2025
@rafaellehmkuhl rafaellehmkuhl self-assigned this Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ux Has to do with the user experience
Projects
None yet
Development

No branches or pull requests

1 participant