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

[BUG] Visualizations cannot use minimum interval Auto in a date histogram if the selected time field isn't the default time field for a given index pattern #9177

Open
jhenley-icr-team opened this issue Jan 13, 2025 · 1 comment
Labels
bug Something isn't working untriaged

Comments

@jhenley-icr-team
Copy link

jhenley-icr-team commented Jan 13, 2025

Describe the bug

Currently when attempting to use a date histogram it is impossible to select minimum interval Auto for any timestamp other than the default Time field for the index pattern that is being visualized.
This is a problem as we don't want to create different index patterns to allow users to set minimum interval auto for each time field they might want to utilize.

To Reproduce
Steps to reproduce the behavior:

  1. For an index pattern with multiple available Date Fields and one as the selected Time Field for the index pattern
  2. Attempt to create a visualization with an x axis date histogram.
  3. Select the default time field and set the minimum interval to Auto
  4. switch to one of the other available date fields
  5. An error should appear like the below
  6. It is impossible to select Auto as it no longer exists in the list of options, for the newly selected date field

Screenshot from 2025-01-13 12-20-20

Expected behavior
Would be useful if minimum interval auto could be utilized for all availible date fields

OpenSearch Version
2.18.0

Dashboards Version
2.18.0

Plugins

NA

Screenshots

Screenshot from 2025-01-13 12-21-02
Screenshot from 2025-01-13 12-20-20

@jhenley-icr-team jhenley-icr-team added bug Something isn't working untriaged labels Jan 13, 2025
@jhenley-icr-team
Copy link
Author

elastic/kibana#3028

After looking through the code noticed this comment, arguably that would make this story more of an enhancement

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged
Projects
None yet
Development

No branches or pull requests

1 participant