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

   ### 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
   
   1. After creating a new workflow through the workflow definition, modify one 
of the task nodes in the task definition, and the pre-task node in the open 
window is lost.
   2. When adding a new task through task definition, you must select a 
predecessor task, and the workflow name and workflow status of other tasks in 
the current workflow will be lost.
   3. When modifying a task through task definition, the content must be 
changed, otherwise the workflow name and workflow status of the current task 
will be lost.
   
   ### What you expected to happen
   
   fix bugs
   
   ### How to reproduce
   
   1. After creating a new workflow through the workflow definition, modify one 
of the task nodes in the task definition, and the pre-task node in the open 
window is lost.
   2. When adding a new task through task definition, you must select a 
predecessor task, and the workflow name and workflow status of other tasks in 
the current workflow will be lost.
   3. When modifying a task through task definition, the content must be 
changed, otherwise the workflow name and workflow status of the current task 
will be lost.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   dev
   
   ### 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