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

Common time formatter #110

Closed
3 of 4 tasks
markov00 opened this issue Mar 20, 2019 · 1 comment
Closed
3 of 4 tasks

Common time formatter #110

markov00 opened this issue Mar 20, 2019 · 1 comment
Labels
:data Data/series/scales related issue enhancement New feature or request kibana cross issue Has a Kibana issue counterpart

Comments

@markov00
Copy link
Member

markov00 commented Mar 20, 2019

We have various implementation in Kibana of timeseries, each of them have its own way to format ticks and labels depending on the interval visualized.

I'd like to have a common implementation that take in consideration as many rules/edgecases as possible to have an unique time formatter usable for all the charts.

The idea is to collect in this issue all the various way we are formatting dates in Kibana to unify them into a common formatter.

Kibana Cross Issues

Checklist

  • this request is checked against already exist requests
  • every related Kibana issue is listed under Kibana Cross Issues list
  • kibana cross issue tag is associated to the issue if any kibana cross issue is present
@markov00 markov00 added enhancement New feature or request kibana cross issue Has a Kibana issue counterpart labels Mar 20, 2019
@markov00 markov00 added the :data Data/series/scales related issue label Mar 26, 2020
@markov00
Copy link
Member Author

This can be closed as the new multi-layer time axis is implemented and available

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:data Data/series/scales related issue enhancement New feature or request kibana cross issue Has a Kibana issue counterpart
Projects
None yet
Development

No branches or pull requests

1 participant