-
Notifications
You must be signed in to change notification settings - Fork 17
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
Feature request, include on top right in our menu a login/logout button #121
Comments
Thank you @GeorgLink for the request. Actually login buttons UX patterns are very diverse, so there is no "where they must be". I would say that's a Kibana "issue", not a GrimoireLab issue. My recommendation would be to open an issue in upstream Kibana project. |
The feature request comes from customer feedback. Sure, it's a Kibana issue. But 1) I don't see us merging new Kibana features into our downstream version. and 2) we have a custom menu at the top and could implement a login button there. |
My suggestion would be to avoid any development in Kibiter, and ask for any Kibana feature to upstream Kibana. GrimoireLab is a toolkit to gather, to process, and to consume software development data that relies on some third parties components for a reference implementation, like Elasticsearch, and Kibana. But users should be available to use other components, specially, for data consumption, like Grafana, Jupiter Notebooks, or even custom JS data visualization frameworks. So, improvements in data visualization tools, should be an issue for such tools, not for GrimoireLab. |
Related: chaoss/grimoirelab#244 |
FYI, it seems that in latest versions of Kibana, like the one included in Open Distro for Elasticsearch 1.2, the logout button is in the top right ;-) |
Login buttons are expected to be on the top right.
Feature request: Include on the top right a menu item that says "Login"
That would significantly improve a new-user's experience.
Optional "awesome" extra: the button changes to "Logout" for logged-in users.
The text was updated successfully, but these errors were encountered: