Skip to content

Dashboard Fix Y Axis for range #11752

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

Merged
merged 1 commit into from
Oct 27, 2017

Conversation

osrecio
Copy link
Member

@osrecio osrecio commented Oct 25, 2017

Fix Dashboard y-axis range qty

Description

Add index for range y-axis

Fixed Issues (if relevant)

  1. Dashboard graph has broken y-axis range #7927: Dashboard graph has broken y-axis range

Manual testing scenarios

  1. Make few orders and look at the graph in admin dashboard
  2. Check Y-axis range is ok

Contribution checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)

@fooman fooman self-assigned this Oct 25, 2017
@fooman fooman added this to the October 2017 milestone Oct 25, 2017
@fooman fooman added Release Line: 2.3 2.2.x bug report Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Progress: accept labels Oct 25, 2017
@okorshenko okorshenko merged commit 914ab8c into magento:2.3-develop Oct 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Progress: accept Release Line: 2.3 Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants