Skip to content

Incorrect x-axis labeling in Charging Sessions chart #16909

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

Closed
1 task done
JanDragon opened this issue Oct 27, 2024 · 2 comments · Fixed by #16919
Closed
1 task done

Incorrect x-axis labeling in Charging Sessions chart #16909

JanDragon opened this issue Oct 27, 2024 · 2 comments · Fixed by #16919
Assignees
Labels
bug Something isn't working ux User experience/ interface

Comments

@JanDragon
Copy link
Contributor

JanDragon commented Oct 27, 2024

Describe the bug

In the "Charging Sessions" chart under the "Total" view, the x-axis is labeled with numbers (0, 1, 2) instead of displaying the years, which would be the expected labels for a "Year" overview. This is misleading, as it suggests the x-axis is showing a sequence rather than specific years. Notably, the tooltip or hover correctly displays the years, but this information is missing in the default view of the x-axis.

Steps to reproduce

  1. Go to the "Charging Sessions" section.
  2. Switch to "Total" view and select "Year" as the display mode.
  3. Observe the x-axis labeling.

What type of operating system are you running?

Linux

Nightly build

  • I have verified that the issue is reproducible with the latest nightly build

Version

0.131.2

Bildschirmfoto 2024-10-27 um 16 38 34

@andig andig added bug Something isn't working ux User experience/ interface labels Oct 27, 2024
@VolkerK62
Copy link
Contributor

same in the "month" view. The days starting with 0

@naltatis
Copy link
Member

regression from #16867

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

Successfully merging a pull request may close this issue.

4 participants