Skip to content

[Fix-18307][API] The frontend is correctly using the preferred values of the associated project for task creating and workflow scheduling#18308

Open
njnu-seafish wants to merge 3 commits into
apache:devfrom
njnu-seafish:Fix-18307
Open

[Fix-18307][API] The frontend is correctly using the preferred values of the associated project for task creating and workflow scheduling#18308
njnu-seafish wants to merge 3 commits into
apache:devfrom
njnu-seafish:Fix-18307

Conversation

@njnu-seafish
Copy link
Copy Markdown
Contributor

Was this PR generated or assisted by AI?

Yes.

Purpose of the pull request

close #18307

Brief change log

When scheduling the workflow, the frontend correctly applies the project's preference values.

Verify this pull request

This pull request is code cleanup without any test coverage.

(or)

This pull request is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(or)

Pull Request Notice

Pull Request Notice

If your pull request contains incompatible change, you should also add it to docs/docs/en/guide/upgrade/incompatible.md

@njnu-seafish njnu-seafish requested a review from SbloodyS as a code owner June 1, 2026 13:10
@github-actions github-actions Bot added the UI ui and front end related label Jun 1, 2026
@njnu-seafish njnu-seafish changed the title [Fix-18307][API] The frontend is correctly using the preferred values of the associated project for workflow scheduling [Fix-18307][API] The frontend is correctly using the preferred values of the associated project for task creating and workflow scheduling Jun 2, 2026
@njnu-seafish
Copy link
Copy Markdown
Contributor Author

njnu-seafish commented Jun 2, 2026

project preference values are not correctly applied when creating tasks:

[DEBUG] restructureNodeData - Creating new task, applying project preferences
detail-modal.tsx:141 [DEBUG] restructureNodeData - Skipping taskPriority: value=HIGHEST, inData=false
detail-modal.tsx:141 [DEBUG] restructureNodeData - Skipping workerGroup: value=seatunnel, inData=false
detail-modal.tsx:138 [DEBUG] restructureNodeData - Applying environmentCode: 172144649035872

Root Cause:
The item in data check fails because the initial data object does not contain fields like taskPriority or workerGroup. These fields are only added later during the form component initialization.

Solution:
Remove the item in data check and directly assign the project preference values to the data object.

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Jun 2, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

UI ui and front end related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] [API] The frontend is not correctly using the preferred values of the associated project for task creating and workflow scheduling.

2 participants