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

Structured inputs for editable filters #5249

Closed
tbragin opened this issue Oct 30, 2015 · 12 comments
Closed

Structured inputs for editable filters #5249

tbragin opened this issue Oct 30, 2015 · 12 comments

Comments

@tbragin
Copy link
Contributor

tbragin commented Oct 30, 2015

In #1583 we are introducing ability to edit filters. The first phase of this (#5109) calls for a JSON based editor that is very flexible and allows introduction of advanced (arbitrary) filters.

To make it easier to interact with editable filters for common use cases, we should consider introducing form-based editors for common filter types, such as date, string, and number.

Here are some screenshots of how this was presented to the user in Kibana 3
screen shot 2015-10-30 at 11 47 26 am

@elvarb
Copy link

elvarb commented Nov 1, 2015

+1

@davidski
Copy link

davidski commented Nov 1, 2015

Big 👍. This is really the minimum viable level of features for #1583, which is a disappointing implementation. At this rate, Kibana 4 will reach Kibana 3 level of usefulness just in time for the whole thing to be rewritten again in KB5. 😞

@rayl
Copy link

rayl commented Nov 1, 2015

👍 Is there a timeline for 4.4.0?

@fbaligand
Copy link
Contributor

Completely agree with @davidski.
This enhancement is a must so that editable filters are usable.
Up to me, this must be part of Kibana 4.3.0.
It can't wait Kibana 4.4.0.

@jerrac
Copy link

jerrac commented Nov 2, 2015

How complicated would implementing this be? Is it something someone could do without knowing the Kibana codebase inside and out? Could the devs let us know where to start on it?

Basically, if someone created a successful pull request for this feature, could it get into Kibana before 4.3?

I don't think I'd have time to do it myself, but if it's an essential feature for someone who has a lot more invested in Kibana than I do, they might have the resources to point at it if they could get some direction.

@spalger
Copy link
Contributor

spalger commented Nov 2, 2015

Sorry @jerrac but 4.3 went into feature freeze Friday.

@fbaligand
Copy link
Contributor

@spalger waou, already a feature freeze ?
what is the targeted release date ? I mean for the first beta or rc1 ?

@spalger
Copy link
Contributor

spalger commented Nov 2, 2015

The target release date is soon :)

@fbaligand
Copy link
Contributor

Waou, I'm impressed...
Version 4.2.0 was released 1 week ago !

@ninjada
Copy link

ninjada commented Nov 13, 2015

Just updated my kibana nodes to 4.2.0 yesterday, but happy to upgrade again for editable filters! :)

@yami12376
Copy link

So what with that case?

In some version after Kibana 3 can i achieve something like that:

3ece4e18-c5a8-11e5-9d64-a419d05ecc79

?

@fbaligand
Copy link
Contributor

You can already achieve such filtering since Kibana 4.3

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

No branches or pull requests