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

[ML] Data frame analytics feature importance decision path popover broken #90603

Closed
pheyos opened this issue Feb 8, 2021 · 1 comment · Fixed by #91061
Closed

[ML] Data frame analytics feature importance decision path popover broken #90603

pheyos opened this issue Feb 8, 2021 · 1 comment · Fixed by #91061
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Data Frame Analytics ML data frame analytics features :ml v7.12.0

Comments

@pheyos
Copy link
Member

pheyos commented Feb 8, 2021

Found in version

  • 7.12 / master

Browser

  • Chrome

Steps to reproduce

  • Open the results view for a classification job with enabled feature importance
  • Open the decision path popover

Expected result

  • The popover is displayed correctly

Actual result

  • The popover displays []

Additional information

@pheyos pheyos added :ml Feature:Data Frame Analytics ML data frame analytics features labels Feb 8, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

@pheyos pheyos changed the title [ML] Data frame analytics feature importance popover broken [ML] Data frame analytics feature importance decision path popover broken Feb 8, 2021
@walterra walterra added v7.12.0 bug Fixes for quality problems that affect the customer experience labels Feb 8, 2021
@peteharverson peteharverson assigned qn895 and unassigned walterra Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Data Frame Analytics ML data frame analytics features :ml v7.12.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants