github-actions[bot] commented on issue #18265: URL: https://github.com/apache/dolphinscheduler/issues/18265#issuecomment-4455526019
### 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 **I have been using this software for a year. From the first time I used it to now, I deeply feel that this product has too many UI interaction shortcomings** Isn’t the current interaction logic anti-human? In other words, the people who are designing this UI interaction shouldn’t be able to use this product. 1. Why must tasks be bound to workflows? Isn’t it possible to run a single task? 2. The primary and secondary relationship is inverted. Why is the logic of creating a executable task now to create a workflow -> Create a task -> Bind timing, instead of creating the task first and then binding its dependencies and timing in the task. Workflow definition and timing should appear as attributes of the task, or the workflow definition should be changed to be called task dependency, and the dependency relationship should be looked at in depth from the interface task. 3. Irrelevant or infrequently modified areas occupy most of the interface. Why task does not seem to be a main function, the time allocation ratio in work should be Task script: Workflow: Timing = 8:1:1 1. Most of the time, the scripts in the tasks are modified, and the dependencies and timings are basically unchanged. Now the ui task script occupies such a small area, and the others take 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. Modifying a task requires complex interactions and unnecessary steps. Now modify the task script. Steps 1. Offline workflow-》2. Modify the task script and save it-》3. Online task flow-》4. Online timing The only effective steps are 2 and 3. A task draft function can save steps 1 and 4, improving efficiency by 50%. In order to ensure that you don't close the issue with me, I will manually translate it into English for you. **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]
