General: Fix sending bulk email invitations

[Abi107717]

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.

Motivation and Context

Bulk sending self-scheduling invitations failed with a LazyInitializationException. The async email sender tried to access Job data (title, supervising professor, research group) through the Application entity, but this relation was not eagerly fetched in the repository query.

Description

Added a single line in InterviewService.sendSelfSchedulingInvitations() to manually set the already loaded Job
object on the Application before sending the email

Steps for Testing

(locally)

1. Log In as a professor
2. Go to /interviews/overview
3. Choose a process
4. Click on Send invitations, check in console that mail was sent
5. Click on Resend Invitation, check in console mail was sent again

(testserver)

1. Log In as applicant using your tumID
2. Apply for a job
3. Log In as a professor
4. Go to evaluation, view your application
5. Go to /interviews/overview
6. Choose the Process for the Job you applied to
7. Add yourself to the process
8. Click on "Send Invitations" button
9. Verify you got a mail
10. Click on "Resend Invitation
11. Verify you got another mail

Review Progress

Code Review

• Code Review 1

Manual Tests

• Test 1

Test Coverage

Warning: Server tests failed. Coverage could not be fully measured. Please check the workflow logs.

Last updated: 2026-01-22 19:32:35 UTC

[github-actions]

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

[github-actions]

@Abi107717 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]

@Abi107717 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.

[github-actions]

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

[github-actions]

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

[github-actions]

@Abi107717 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]

@Abi107717 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.