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

Allow date picker to have relative dates to start/end rather than 'now' #121167

Closed
Tracked by #163011
stevedearl opened this issue Dec 14, 2021 · 4 comments
Closed
Tracked by #163011
Labels
Feature:FieldFormatters impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:large Large Level of Effort Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph) triage_needed

Comments

@stevedearl
Copy link

This may be a bit of an edge case, but it would be useful for us to be able to select an absolute start date, and then have a relative date of +24h from that start date.
The reverse may also be useful, so that we set an absolute end date and have the ability to set the start date relative to it, say -7 days.

At the moment, we can only set dates relative to 'now'.

Describe a specific use case for the feature:
We monitor error logs from our applications on a 24 hour cycle from 8am-8am every day.
At the moment we need to set both 'start' and 'end' date to absolute values in the datepicker to set the correct timespan. It would be handy to be able to set 'end' date to 8am today and 'start' date to -24h relative to end date.
This is not a major feature by any means but I thought I'd raise it...!

@botelastic botelastic bot added the needs-team Issues missing a team label label Dec 14, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServicesUx)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 15, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:small Small Level of Effort impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:large Large Level of Effort and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:small Small Level of Effort labels Dec 20, 2021
@henrikno
Copy link
Contributor

I don't think this is an edge case, I think this should be the default when picking a date and clicking relative.

@petrklapka petrklapka added Feature:FieldFormatters Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph) and removed Team:AppServicesUx labels Dec 12, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@kertal
Copy link
Member

kertal commented Aug 9, 2023

We are closing this issue in order to provide better transparency of priorities. This issue won't be prioritized in the near future. We track it in #163011 for long term planning.

@kertal kertal closed this as completed Aug 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:FieldFormatters impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:large Large Level of Effort Team:DataDiscovery Discover App Team (Document Explorer, Saved Search, Surrounding documents, Graph) triage_needed
Projects
None yet
Development

No branches or pull requests

5 participants