[PR #20780] [MERGED] fix: restore email/username search support to workspace pages #25782

New Issue

GiteaMirror · 2026-04-20T06:07:20-05:00

GiteaMirror commented

2026-04-20 06:07:20 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/20780
Author: @silentoplayz
Created: 1/18/2026
Status: ✅ Merged
Merged: 1/19/2026
Merged by: @tjbck

Base: dev ← Head: fix/username-search-workspace-pages

📝 Commits (1)

8d554e9 fix: add username search support to workspace and admin pages

📊 Changes

3 files changed (+10 additions, -1 deletions)

View changed files

📝 backend/open_webui/models/knowledge.py (+3 -0)
📝 backend/open_webui/models/models.py (+3 -0)
📝 src/lib/components/admin/Functions.svelte (+4 -1)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.

This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.

Before submitting, make sure you've checked the following:

Target branch: Verify that the pull request targets the dev branch. Not targeting the dev branch will lead to immediate closure of the PR.
Description: Provide a concise description of the changes made in this pull request down below.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: If necessary, update relevant documentation Open WebUI Docs like environment variables, the tutorials, or other documentation sources.
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Take this as an opportunity to make screenshots of the feature/fix and include it in the PR description.
Agentic AI Code: Confirm this Pull Request is not written by any AI Agent or has at least gone through additional human review AND manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Title Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

This fix restores and extends username/email/username search functionality across workspace and admin pages. The original PR #14002 added this feature, but it was incomplete:
Models and Knowledge pages only searched User.name and User.email in the backend, missing User.username
The Functions admin page had no user search capability at all

This PR adds User.username to the backend search conditions for Models and Knowledge, and adds complete user search (name, email, username) to the Functions page client-side filter.

Fixed/Added

Added User.username to search conditions in search_models() function for Models workspace page
Added User.username to search conditions in search_knowledge_bases() function for Knowledge workspace page
Added user name/email/username search to Functions admin page client-side filter

Additional Information

Related to PR #14002 which originally added username/email search across workspace pages
Root cause: Backend search for Models and Knowledge only included User.name and User.email fields, missing User.username
The Functions page (admin panel) was also missing user search functionality

Before

After

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.

Note

Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/20780 **Author:** [@silentoplayz](https://github.com/silentoplayz) **Created:** 1/18/2026 **Status:** ✅ Merged **Merged:** 1/19/2026 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `fix/username-search-workspace-pages` --- ### 📝 Commits (1) - [`8d554e9`](https://github.com/open-webui/open-webui/commit/8d554e9bfd021b89028768ca6a7d5cf6b79de3e4) fix: add username search support to workspace and admin pages ### 📊 Changes **3 files changed** (+10 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/models/knowledge.py` (+3 -0) 📝 `backend/open_webui/models/models.py` (+3 -0) 📝 `src/lib/components/admin/Functions.svelte` (+4 -1) </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request. This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR. **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Verify that the pull request targets the `dev` branch. **Not targeting the `dev` branch will lead to immediate closure of the PR.** - [x] **Description:** Provide a concise description of the changes made in this pull request down below. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [x] **Documentation:** If necessary, update relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs) like environment variables, the tutorials, or other documentation sources. - [x] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [x] **Testing:** Perform manual tests to **verify the implemented fix/feature works as intended AND does not break any other functionality**. Take this as an opportunity to **make screenshots of the feature/fix and include it in the PR description**. - [x] **Agentic AI Code:** Confirm this Pull Request is **not written by any AI Agent** or has at least **gone through additional human review AND manual testing**. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR. - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Title Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description - This fix restores and extends username/email/username search functionality across workspace and admin pages. The original PR #14002 added this feature, but it was incomplete: - Models and Knowledge pages only searched User.name and User.email in the backend, missing User.username - The Functions admin page had no user search capability at all This PR adds `User.username` to the backend search conditions for Models and Knowledge, and adds complete user search (name, email, username) to the Functions page client-side filter. ### Fixed/Added - Added `User.username` to search conditions in `search_models() function` for Models workspace page - Added `User.username` to search conditions in `search_knowledge_bases() function` for Knowledge workspace page - Added user name/email/username search to Functions admin page client-side filter --- ### Additional Information - Related to PR #14002 which originally added username/email search across workspace pages - Root cause: Backend search for Models and Knowledge only included `User.name` and `User.email` fields, missing `User.username` - The Functions page (admin panel) was also missing user search functionality ### Before <img width="2315" height="614" alt="image" src="https://github.com/user-attachments/assets/6f4790c5-c66b-4b87-ae5c-48c0817aee9a" /> ### After <img width="2315" height="614" alt="image" src="https://github.com/user-attachments/assets/8a705cf7-ce94-4ef6-93e4-dbb51103ca7d" /> ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. > [!NOTE] > Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-20 06:07:21 -05:00

GiteaMirror closed this issue

2026-04-20 06:07:21 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#25782