Skip to content

Interview: link to the full application from the interviewee card#1927

Open
rappm wants to merge 1 commit into
mainfrom
1199-interviewee-card-application-link
Open

Interview: link to the full application from the interviewee card#1927
rappm wants to merge 1 commit into
mainfrom
1199-interviewee-card-application-link

Conversation

@rappm

@rappm rappm commented Jul 15, 2026

Copy link
Copy Markdown
Member

📝 Pull Request Template

Use this template to provide all necessary information for reviewing and testing your changes.

✨ What is the change?

Adds a "View full application" action to the interviewee card (StudentCard). It deep-links to the applicant's participant detail in the course's Application phase (/management/course/<courseId>/<applicationPhaseId>/participants/<participationId>).

The target Application phase is resolved from the course store; the action is hidden when the course has no Application phase. On the overview grid the click is stopped from bubbling so it doesn't also open the interview detail.

📌 Reason for the change / Link to issue

Interviewers wanted more context (full application, previous courses, …) from the interviewee card. The linked application detail page already renders the full application answers and the student's previous-course enrollments, so a single link surfaces that context without duplicating it here.

Note: showing previous-course enrollments inline in the interview card is intentionally not part of this PR. The only enrollments endpoint (/api/students/:id/enrollments) requires the instance-wide PROMPT_Lecturer/admin role, so a regular course lecturer gets a 403; doing it inline for them would need a new phase-scoped backend endpoint. That is left as a follow-up.

Part of #1199

🧪 How to Test

  1. Open a course that has both an Application and an Interview phase.
  2. Go to the Interview phase → Manage (overview grid) as an admin or course lecturer.
  3. On any interviewee card, click View full application → you land on that applicant's application detail page (full answers + previous courses).
  4. Open an interviewee's detail view; the same action is available on the card there.
  5. On a course with no Application phase, the action is not shown.

🖼️ Screenshots (if UI changes are included)

Before After
before after

✅ PR Checklist

  • Tested locally or on the dev environment
  • Code is clean, readable, and documented
  • Tests added or updated (if needed)
  • Screenshots attached for UI changes (if any)
  • Documentation updated (if relevant)

Add a "View full application" action to the interviewee card that
deep-links to the applicant's participant detail in the course's
Application phase. That page shows the full application answers and the
student's previous-course enrollments, so interviewers get the extra
context without leaving the flow.

The Application phase is resolved from the course store; the action is
hidden when the course has no Application phase. Auth aligns: both the
interview management pages and the application detail route require
PromptAdmin or CourseLecturer.

Part of #1199
@rappm
rappm requested a review from a team July 15, 2026 15:10
@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@rappm, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 16 seconds

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0a570c9f-b7c2-4cff-bd20-97e5ae501555

📥 Commits

Reviewing files that changed from the base of the PR and between a4c7721 and c7eb883.

📒 Files selected for processing (1)
  • clients/interview_component/src/interview/components/StudentCard.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 1199-interviewee-card-application-link

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@rappm rappm added the schau mi o Translation: Ready to review label Jul 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

schau mi o Translation: Ready to review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Interview: show more info from application, previous courses, etc in the interviewee card

1 participant