csdog opened a new issue, #18265: URL: https://github.com/apache/dolphinscheduler/issues/18265
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description **用了有1年的时间这款软件了，从我第一次使用，到现在，我深深的感觉这款产品的ui交互槽点实在太多了** 现在的交互逻辑不反人类吗，或者说设计现在的做出这款ui交互的人应该也不会用这款产品吧 1. 为什么任务一定要绑定工作流? 单独一个任务运行不行吗 2. 主次关系倒置，为什么 现在创建一个能运行的任务的逻辑是 创建工作流-》创建任务 -》 绑定定时， 而不是先创建任务，再在任务里绑定其依赖关系和定时 。工作流定义、定时 应该是作为任务的属性出现，或者工作流定义应该改成叫任务依赖，从界面任务再深度进去看依赖关系。 3. 无关紧要的或者修改频率低的地方占了界面绝大部分版面。为什么任务 看起来不是一个主要的功能，工作中的时间分配比应该是是 任务脚本：工作流：定时=8:1:1 1. 绝大多数时间都是在修改任务中的脚本，依赖关系和定时 基本都不变，而现在ui这任务脚本占地这么一小块，其他的占了绝大部分界面 <img width="1220" height="3510" alt="Image" src="https://github.com/user-attachments/assets/79494514-e389-4d59-b4d0-68966eefe00a"; /> 4. 修改一次任务交互复杂，没必要的步骤多。现在修改一下任务脚本 步骤 1.下线工作流-》2.修改任务脚本保存-》3.上线任务流-》4.上线定时 有效步骤也就2，3， 一个任务草稿功能能将步骤1，4省了，50%的效率提升 为了保证你们别给我close issue，我再手动给你翻译成英文。 **I've been using this software for one year. From the first time I used it until now, I deeply feel that there are too many UI interaction issues with this product.** Isn't the current interaction logic against human intuition? Or perhaps the person who designed this UI wouldn't even use this product? 1. Why must tasks be tied to workflows? Can't a single task run independently? 2. The primary-secondary relationship is inverted. Why is the logic for creating a runnable task now: Create Workflow -> Create Task -> Bind Schedule, instead of creating the task first and then binding its dependencies and schedule within the task? Workflow definitions and schedules should appear as task properties, or workflow definitions should be renamed as task dependencies, and dependencies should be viewable in-depth from the task interface. 3. Unimportant or rarely modified areas take up most of the interface. Why do tasks seem not to be the main function? In actual work, the time allocation ratio should be: task scripts: workflows: schedules = 8:1:1. Most of the time is spent editing task scripts, while dependencies and schedules basically remain unchanged, yet in the current UI, task scripts occupy such a small area, and everything else takes up most of the interface. <img width="1220" height="3510" alt="Image" src="https://github.com/user-attachments/assets/79494514-e389-4d59-b4d0-68966eefe00a"; /> 4. Editing a task is a complex interaction with unnecessary steps. Currently, to modify a task script, the steps are: 1. take workflow offline -> 2. modify task script and save -> 3. bring workflow online -> 4. bring schedule online. The effective steps are really just 2 and 3. A task draft function could eliminate steps 1 and 4, improving efficiency by 50%. To make sure you don’t close this issue on me, I’ve manually translated it into English. ### Are you willing to submit a PR? - [ ] 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]
