github-actions[bot] commented on issue #18405:
URL: 
https://github.com/apache/dolphinscheduler/issues/18405#issuecomment-4931805927

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   Version / 版本号
   
   3.1.4
   
   Please describe the bug here / 问题描述
   
   English:
   In the DEPENDENT task node's "Add Dependency" configuration dialog, after 
selecting a Project Name, the Workflow Name field is a searchable/filterable 
select. Clicking the dropdown without typing anything correctly shows the full 
list of online (已上线) workflow definitions under the selected project.
   
   However, typing any text into the Workflow Name input to filter the list 
returns no results ("无数据" / No Data), even when the typed text is clearly a 
substring of multiple visible workflow names in the full (unfiltered) list.
   
   Example: the project contains workflows named 
wf_ods_yinta_yt_amz_bad_review_details, 
wf_ods_amz_report_t_amz_inventory_all_..., wf_ods_lv1_job, etc. — all starting 
with wf. Typing wf into the search box returns an empty list, instead of 
matching all of them.
   
   This suggests the client-side filter is not matching against the option's 
display label (workflow name text), and may instead be filtering against the 
option's underlying value (likely the numeric processDefinitionCode), which 
would never match a text query like "wf".
   
   中文:
   在 
DEPENDENT(依赖)任务节点的"添加依赖"配置弹窗中,选择好项目名称后,"工作流名称"是一个可搜索/可过滤的下拉选择框。不输入任何字符、直接点开下拉框时,能正常显示该项目下全部已上线的工作流定义列表。
   
   但是,在"工作流名称"输入框中输入任意文字进行过滤时,即使输入的内容明显是完整列表中多个工作流名称的子串,结果依然显示"无数据"(空列表)。
   
   例如:项目中存在名为 
wf_ods_yinta_yt_amz_bad_review_details、wf_ods_amz_report_t_amz_inventory_all_...、wf_ods_lv1_job
 等工作流,全部以 "wf" 开头。在搜索框中输入 "wf",返回的却是空列表,而不是匹配这些工作流。
   
   这说明前端的过滤逻辑并没有按照选项的展示文本(工作流名称)去做匹配,很可能是在按选项底层的 value 字段(大概率是数字类型的 
processDefinitionCode)做匹配,这样文本查询(如 "wf")永远不可能命中一个纯数字字段。
   
   <img width="644" height="859" alt="Image" 
src="https://github.com/user-attachments/assets/e5f8dbd4-8d73-4578-9834-a36b1e8801d5";
 />
   <img width="636" height="845" alt="Image" 
src="https://github.com/user-attachments/assets/8ef9ae42-08b6-4c73-837f-4ccd8c3e4225";
 />
   
   ### What you expected to happen
   
   English: Typing a substring of a workflow's name (e.g. "wf") in the Workflow 
Name field of the DEPENDENT task dialog should filter and show all matching 
workflows by name, consistent with how workflow-name search works elsewhere in 
the UI (e.g. the Workflow Definition list page).
   
   中文: 在依赖节点弹窗的"工作流名称"输入框中输入名称子串(例如 "wf"),应当能按名称正确过滤并展示所有匹配的工作流,与 UI 
其他位置(如工作流定义列表页)的名称搜索行为保持一致。
   
   ### How to reproduce
   
   Open a workflow definition, add/edit a DEPENDENT task. / 打开一个工作流定义,新增或编辑一个 
DEPENDENT 任务节点。
   Click "Add Dependency" (添加依赖). / 点击"添加依赖"。
   Select a Project Name that has multiple online workflow definitions. / 
选择一个含有多个已上线工作流的项目名称。
   Click into the Workflow Name field — confirm the full dropdown list appears 
with data. / 点击"工作流名称"输入框,确认下拉列表能正常展示完整数据。
   Type a short substring that matches several workflow names in that list 
(e.g. a common prefix like "wf"). / 输入一个能匹配多个工作流名称的子串(例如常见前缀 "wf")。
   Observe the dropdown shows "无数据" / No Data, even though multiple workflows 
visibly contain that substring. / 观察到下拉框显示"无数据",即使列表中明显有多个工作流名称包含该子串。
   
   ### Anything else
   
   Note: The version dropdown above doesn't list 3.1.4 (an older release), so I 
selected the closest available option. The actual version in use is 3.1.4 — see 
the java.class.path output in the bug description for confirmation.
   
   
   说明: 上方版本下拉框未列出 3.1.4(较早版本),因此选择了列表中最接近的选项。实际使用版本为 3.1.4——详见问题描述中 
java.class.path 输出的确认信息。
   
   
   ### Version
   
   3.3.2
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to