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] Per partition categorization - cloning doesn't take over partition field correctly #86279

Closed
pheyos opened this issue Dec 17, 2020 · 1 comment · Fixed by #86635
Closed
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Anomaly Detection ML anomaly detection :ml v7.11.0

Comments

@pheyos
Copy link
Member

pheyos commented Dec 17, 2020

Found in version

  • 8.0.0

Browser

  • Chrome

Steps to reproduce

  • Create a per partition categorization job where the partition field is not the first entry of the list
  • Clone that job

Expected result

  • The wizard pre-fills the partition field for the clone with the field name selected in the original job

Actual result

  • The wizard pre-fills the partition field with the first entry of the list
@pheyos pheyos added bug Fixes for quality problems that affect the customer experience :ml Feature:Anomaly Detection ML anomaly detection labels Dec 17, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/ml-ui (:ml)

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:Anomaly Detection ML anomaly detection :ml v7.11.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants