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

[Index pattern creation] Move "Unable to fetch mappings" error closer to index pattern text field #11410

Closed
ycombinator opened this issue Apr 25, 2017 · 0 comments
Assignees
Labels

Comments

@ycombinator
Copy link
Contributor

As soon as a user types in an index pattern, Kibana tries to fetch that index pattern from Elasticsearch. If it is unable to fetch any indices, it disables the button to create the index pattern and shows an error message as the button's value:

The error message is visually disconnected from its source: the text field where the user entered the index pattern. We should move the error message out of the button and right under the index pattern text field. The button disabling behavior should be preserved.

@ycombinator ycombinator added the good first issue low hanging fruit label Apr 28, 2017
@chrisronline chrisronline self-assigned this May 15, 2017
chrisronline added a commit to chrisronline/kibana that referenced this issue May 15, 2017
chrisronline added a commit that referenced this issue May 16, 2017
…eld (#11801)

* Move the error message to below the input field, resolves #11410

* Update to match HTML styleguide
chrisronline added a commit that referenced this issue May 16, 2017
…eld (#11801)

* Move the error message to below the input field, resolves #11410

* Update to match HTML styleguide
snide pushed a commit to snide/kibana that referenced this issue May 30, 2017
…eld (elastic#11801)

* Move the error message to below the input field, resolves elastic#11410

* Update to match HTML styleguide
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants