General: Code clean up for prior employee fixes

[sachmii]

Checklist

General

• I tested all changes and their related features with all corresponding user types.
• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Server

• Important: I implemented the changes with a very good performance and prevented too many (unnecessary) and too complex database calls.
• I strictly followed the principle of data economy for all database calls.
• I strictly followed the server coding and design guidelines.
• I documented the Java code using JavaDoc style.

Client

• Important: I implemented the changes with a very good performance, prevented too many (unnecessary) REST calls and made sure the UI is responsive, even with large data (e.g. using paging).
• I strictly followed the principle of data economy for all client-server REST calls.
• I strictly followed the client coding and design guidelines.
• I added multiple integration tests (Jest) related to the features (with a high test coverage), while following the test guidelines.
• I documented the TypeScript code using JSDoc style.

Motivation and Context

Code clean up for a prior PR. Closes #1905.

Description

• Added a research-group professors endpoint and updated the job creation flow to consume it, simplifying supervising‑professor normalization and loading logic.
• Renamed the research‑group jobs endpoint/service method (from professor‑scoped naming) and updated related frontend calls, mocks, and tests.
• Introduced UserNotFoundException for supervising‑professor lookup failures.
• Adjusted init/load behavior to reduce redundant requests and keep selections consistent.
• Added more tests for my-positions-page.

Steps for Testing

Prerequisites:

1. Log in to TumApply as Employee
2. Try to create a positions
3. Should preselect one professor of the research group as supervising professor

Review Progress

Code Review

• Code Review 1

Manual Tests

• Test 1

Test Coverage

Warning: Both client and server tests failed. Coverage could not be fully measured. Please check the workflow logs.

Last updated: 2026-02-13 14:09:29 UTC

Screenshots

[github-actions]

@sachmii Test coverage could not be fully measured because some tests failed. Please check the workflow logs for details.

[github-actions]

@sachmii Test coverage has been automatically updated in the PR description.

[github-actions]

@sachmii Test coverage could not be fully measured because some tests failed. Please check the workflow logs for details.

[github-actions]

🤖 OpenAPI spec and client code auto-updated and committed.

[github-actions]

@sachmii Test coverage could not be fully measured because some tests failed. Please check the workflow logs for details.

[github-actions]

🤖 No OpenAPI or client changes needed.

[Bofan-Zhu]

Thanks for adding this. I left a few comments on the code (did not test it)

[github-actions]

@sachmii Test coverage could not be fully measured because some tests failed. Please check the workflow logs for details.

[github-actions]

🤖 No OpenAPI or client changes needed.