Improve scorer trace picker UX and validation#20178
Merged
danielseong1 merged 1 commit intomlflow:masterfrom Jan 22, 2026
Merged
Improve scorer trace picker UX and validation#20178danielseong1 merged 1 commit intomlflow:masterfrom
danielseong1 merged 1 commit intomlflow:masterfrom
Conversation
Contributor
🛠 DevTools 🛠
Install mlflow from this PRFor Databricks, use the following command: |
Contributor
|
Documentation preview for 31bdb7e is available at: More info
|
This PR makes two improvements to the scorer evaluation UI:
1. Remove "Last trace/session" dropdown option - Users must now explicitly
select traces/sessions via the modal picker. This simplifies the UI and
makes trace selection more intentional.
2. Disable "Run judge" button for non-gateway models - Direct model endpoints
are not supported for running judges from the UI, so the button is now
disabled with an explanatory tooltip.
Key changes:
- Simplified `itemsToEvaluate` state from `{ itemCount, itemIds }` to just `selectedItemIds: string[]`
- Replaced dropdown with a simple button that opens the selection modal
- Added validation to disable run button when no traces are selected
- Added validation to disable run button for direct (non-gateway) models
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Daniel Seong <daniel.leem.seong@gmail.com>
1709b5b to
31bdb7e
Compare
smoorjani
approved these changes
Jan 21, 2026
Collaborator
smoorjani
left a comment
There was a problem hiding this comment.
LGTM, thanks for the fixes!
harupy
pushed a commit
to harupy/mlflow
that referenced
this pull request
Jan 28, 2026
Signed-off-by: Daniel Seong <daniel.leem.seong@gmail.com> Co-authored-by: Daniel Seong <daniel.leem.seong@gmail.com> Co-authored-by: Claude <noreply@anthropic.com>
harupy
pushed a commit
to harupy/mlflow
that referenced
this pull request
Jan 28, 2026
Signed-off-by: Daniel Seong <daniel.leem.seong@gmail.com> Co-authored-by: Daniel Seong <daniel.leem.seong@gmail.com> Co-authored-by: Claude <noreply@anthropic.com>
harupy
pushed a commit
that referenced
this pull request
Jan 28, 2026
Signed-off-by: Daniel Seong <daniel.leem.seong@gmail.com> Co-authored-by: Daniel Seong <daniel.leem.seong@gmail.com> Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
This PR makes two adjustments to the scorer evaluation UI based on UX feedback:
Remove "Last trace/session" dropdown option - Users must now explicitly select traces/sessions via the modal picker. This simplifies the UI and makes trace selection more intentional.
Disable "Run judge" button for non-gateway models - Direct model endpoints are not supported for running judges from the UI, so the button is now disabled with an explanatory tooltip.
Key changes:
itemsToEvaluatestate from{ itemCount, itemIds }to justselectedItemIds: string[]How is this PR tested?
Updated existing unit tests to reflect the simplified state shape. Manually verified the UI changes work correctly.
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/tracking: Tracking Service, tracking client APIs, autologgingarea/models: MLmodel format, model serialization/deserialization, flavorsarea/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registryarea/scoring: MLflow Model server, model deployment tools, Spark UDFsarea/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflowsarea/gateway: MLflow AI Gateway client APIs, server, and third-party integrationsarea/prompts: MLflow prompt engineering features, prompt templates, and prompt managementarea/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionalityarea/projects: MLproject format, project running backendsarea/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow should the PR be classified in the release notes? Choose one:
rn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change- The PR will be mentioned in the "Breaking Changes" sectionrn/feature- A new user-facing feature worth mentioning in the release notesrn/bug-fix- A user-facing bug fix worth mentioning in the release notesrn/documentation- A user-facing documentation change worth mentioning in the release notesShould this PR be included in the next patch release?
🤖 Generated with Claude Code