Skip to content

[ML-61124]: add selector for workflow type in top level navbar#20158

Merged
daniellok-db merged 1 commit intomlflow:masterfrom
ispoljari:ML61124/implement-selector-for-workflow-type-in-top-level-navbar
Jan 22, 2026
Merged

[ML-61124]: add selector for workflow type in top level navbar#20158
daniellok-db merged 1 commit intomlflow:masterfrom
ispoljari:ML61124/implement-selector-for-workflow-type-in-top-level-navbar

Conversation

@ispoljari
Copy link
Collaborator

@ispoljari ispoljari commented Jan 20, 2026 •
edited by daniellok-db
Loading

This PR contains the entire feature: #20161

Related Issues/PRs

[ML-61124]

What changes are proposed in this pull request?

This PR implements a workflow type selector in the top-level sidebar that allows users to switch between "GenAI" and "Machine Learning" workflows. The selected workflow type is stored in localStorage and made available throughout the application via a React context (useWorkflowType hook).

Key changes:

  • Added WorkflowType enum and WorkflowTypeContext with useWorkflowType hook
  • Implemented workflow type selector UI in MlflowSidebar.tsx using SegmentedControlGroup
  • Integrated WorkflowTypeProvider in MlflowRouter.tsx to provide context to all routes
  • Persisted workflow type selection in localStorage with versioning support

How is this PR tested?

  • Existing unit/integration tests
  • New unit/integration tests
  • Manual tests
Screenshot 2026-01-20 at 15 47 37 Screenshot 2026-01-20 at 15 47 52

Does this PR require documentation update?

  • No. You can skip the rest of this section.
  • Yes. I've updated:
    • Examples
    • API references
    • Instructions

Release Notes

Is this a user-facing change?

  • No. You can skip the rest of this section.
  • Yes. Give a description of this change to be included in the release notes for MLflow users.

Added a workflow type selector in the sidebar to switch between GenAI and Machine Learning workflows. The selection is persisted and available throughout the application.

What component(s), interfaces, languages, and integrations does this PR affect?

Components

  • area/tracking: Tracking Service, tracking client APIs, autologging
  • area/models: MLmodel format, model serialization/deserialization, flavors
  • area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
  • area/scoring: MLflow Model server, model deployment tools, Spark UDFs
  • area/evaluation: MLflow model evaluation features, evaluation metrics, and evaluation workflows
  • area/gateway: MLflow AI Gateway client APIs, server, and third-party integrations
  • area/prompts: MLflow prompt engineering features, prompt templates, and prompt management
  • area/tracing: MLflow Tracing features, tracing APIs, and LLM tracing functionality
  • area/projects: MLproject format, project running backends
  • area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server
  • area/build: Build and test infrastructure for MLflow
  • area/docs: MLflow documentation pages

How 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" section
  • rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
  • rn/feature - A new user-facing feature worth mentioning in the release notes
  • rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
  • rn/documentation - A user-facing documentation change worth mentioning in the release notes

Should this PR be included in the next patch release?

Yes should be selected for bug fixes, documentation updates, and other small changes. No should 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?
  • Minor release: a release that increments the second part of the version number (e.g., 1.2.0 -> 1.3.0).
    Bug fixes, doc updates and new features usually go into minor releases.
  • Patch release: a release that increments the third part of the version number (e.g., 1.2.0 -> 1.2.1).
    Bug fixes and doc updates usually go into patch releases.
  • Yes (this PR will be cherry-picked and included in the next patch release)
  • No (this PR will be included in the next minor release)

@github-actions
Copy link
Contributor

github-actions bot commented Jan 20, 2026

🛠 DevTools 🛠

Install mlflow from this PR

# mlflow
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/20158/merge
# mlflow-skinny
pip install git+https://github.com/mlflow/mlflow.git@refs/pull/20158/merge#subdirectory=libs/skinny

For Databricks, use the following command:

%sh curl -LsSf https://raw.githubusercontent.com/mlflow/mlflow/HEAD/dev/install-skinny.sh | sh -s pull/20158/merge

@github-actions
Copy link
Contributor

github-actions bot commented Jan 20, 2026

@ispoljari Thank you for the contribution! Could you fix the following issue(s)?

⚠ DCO check

The DCO check failed. Please sign off your commit(s) by following the instructions here. See https://github.com/mlflow/mlflow/blob/master/CONTRIBUTING.md#sign-your-work for more details.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 20, 2026 •
edited
Loading

Documentation preview for 0c16dab is available at:

More info
  • Ignore this comment if this PR does not change the documentation.
  • The preview is updated when a new commit is pushed to this PR.
  • This comment was created by this workflow run.
  • The documentation was built by this workflow run.

@ispoljari ispoljari mentioned this pull request Jan 20, 2026
Merged
29 tasks
@github-actions github-actions bot added area/uiux Front-end, user experience, plotting, JavaScript, JavaScript dev server rn/feature Mention under Features in Changelogs. labels Jan 20, 2026
daniellok-db
daniellok-db approved these changes Jan 21, 2026
View reviewed changes
Copy link
Collaborator

@daniellok-db daniellok-db left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lg!

daniellok-db
daniellok-db reviewed Jan 21, 2026
View reviewed changes
@ispoljari ispoljari force-pushed the ML61124/implement-selector-for-workflow-type-in-top-level-navbar branch 8 times, most recently from 0f695d9 to e6ee3bc Compare January 22, 2026 02:11
@ispoljari
[ML-61124]: add selector for workflow type in top level navbar
0c16dab 
[ML-61124]: update translation labels

[ML-61124]: add feature flag

Remove databricks serving endpoint adapter and redirect databricks managed models to litellm adapter (mlflow#20037)

Signed-off-by: Xiang Shen <xshen.shc@gmail.com>
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>

[ML-61125]: set shouldEnableWorkflowBasedNavigation to false

[ML-61124]: sidebar width

[ML-61125]: resolve conflict
@ispoljari ispoljari force-pushed the ML61124/implement-selector-for-workflow-type-in-top-level-navbar branch from e6ee3bc to 0c16dab Compare January 22, 2026 02:11
@daniellok-db daniellok-db added this pull request to the merge queue Jan 22, 2026
Merged via the queue into mlflow:master with commit 17e1af3 Jan 22, 2026
50 of 52 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@daniellok-db daniellok-db daniellok-db approved these changes

@hubertzub-db hubertzub-db Awaiting requested review from hubertzub-db

Assignees

@daniellok-db daniellok-db

Labels

area/uiux Front-end, user experience, plotting, JavaScript, JavaScript dev server rn/feature Mention under Features in Changelogs.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ispoljari @daniellok-db