HanadaLee opened a new issue, #15151: URL: https://github.com/apache/dolphinscheduler/issues/15151
### 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 Currently, a workflow can only use one scheduled task, so why provide a separate timing management tab for workflow timing. In my opinion, workflow and scheduled planning should have a one-to-many relationship.  As shown in the figure, after turning on scheduled tasks, you can no longer add scheduled tasks, and clicking on scheduled management only jumps to a list of only one scheduled task. Since there is only one scheduled task management, wouldn’t it be better to directly use the scheduled task as an attribute of the task definition? ### Use case Due to some special timing designs, one crontab configuration cannot meet timing requirements. We hope to provide multiple crontab timings and multiple start and stop times for a workflow. Now it seems that I can only create multiple identical workflows for this, and I must modify all these identical workflows every time I modify them. ### Related issues No ### 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]
