Move select traces button to be next to Run judge#20992
Merged
PattaraS merged 1 commit intomlflow:masterfrom Feb 19, 2026
Merged
Move select traces button to be next to Run judge#20992PattaraS merged 1 commit intomlflow:masterfrom
PattaraS merged 1 commit intomlflow:masterfrom
Conversation
Signed-off-by: Pat Sukprasert <pattara.sk127@gmail.com>
Contributor
🛠 DevTools 🛠
Install mlflow from this PRFor Databricks, use the following command: |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Sample Judge UI layout to place the “Select traces/sessions” control adjacent to the primary “Run judge” action for improved visibility and workflow.
Changes:
- Moved
SampleScorerTracesToEvaluatePickerfrom the output panel header into the empty-state action row next to “Run judge”. - Adjusted the picker button sizing by removing the explicit
size="small"prop.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
mlflow/server/js/src/experiment-tracking/pages/experiment-scorers/SampleScorerTracesToEvaluatePicker.tsx |
Removes explicit small sizing on the picker trigger button. |
mlflow/server/js/src/experiment-tracking/pages/experiment-scorers/SampleScorerOutputPanelRenderer.tsx |
Relocates the picker from the header to the empty-state “Run judge” row. |
Comments suppressed due to low confidence (1)
mlflow/server/js/src/experiment-tracking/pages/experiment-scorers/SampleScorerOutputPanelRenderer.tsx:173
- The traces/sessions picker has been removed from the panel header, so once an evaluation result is shown (or when the error state is displayed) there’s no longer any UI to change the selected traces/sessions before re-running. This looks like a functional regression vs. the previous behavior where selection could be changed at any time. Consider rendering the picker next to the “Re-Run judge” button in the header as well (and/or in the error state action area), so users can adjust the selection for subsequent runs.
<div css={{ display: 'flex', gap: theme.spacing.sm, alignItems: 'center' }}>
{!isInitialScreen && (
<Tooltip
componentId="codegen_no_dynamic_mlflow_web_js_src_experiment_tracking_pages_experiment_scorers_samplescoreroutputpanelrenderer_178"
content={isRunScorerDisabled ? runScorerDisabledTooltip : undefined}
Contributor
|
Documentation preview for 2e67d66 is available at: More info
|
daniellok-db
pushed a commit
to daniellok-db/mlflow
that referenced
this pull request
Feb 20, 2026
Signed-off-by: Pat Sukprasert <pattara.sk127@gmail.com>
daniellok-db
pushed a commit
that referenced
this pull request
Feb 20, 2026
Signed-off-by: Pat Sukprasert <pattara.sk127@gmail.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
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?
As titled.
How is this PR tested?
Before
After
Does this PR require documentation update?
Does this PR require updating the MLflow Skills repository?
Release Notes
Is this a user-facing change?
Move "Select traces" button in the Judge UI to be next to "Run judge" button for better visibility.
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?
Yesshould be selected for bug fixes, documentation updates, and other small changes.Noshould be selected for new features and larger changes. If you're unsure about the release classification of this PR, leave this unchecked to let the maintainers decide.What is a minor/patch release?
Bug fixes, doc updates and new features usually go into minor releases.
Bug fixes and doc updates usually go into patch releases.