Skip to content

Teambuilder Matching & Participant Ranking#9

Open
loleg wants to merge 1 commit intomainfrom
teambuilder-matching-2693533477962168735
Open

Teambuilder Matching & Participant Ranking#9
loleg wants to merge 1 commit intomainfrom
teambuilder-matching-2693533477962168735

Conversation

@loleg
Copy link
Member

@loleg loleg commented Feb 26, 2026

This PR implements a Teambuilder tool for event organizers and a project ranking system for participants.

Key Changes:

  • Participant Ranking: Users can now rank up to 5 projects for the current event using a new drag-and-drop UI (powered by SortableJS). Rankings are stored in a new _my_ranking field in the User model.
  • Admin Teambuilder Dashboard: A new view in the Admin panel allows organizers to see all projects and participants at a glance.
  • Matching Process: Organizers can trigger a matching process that suggests assignments based on participant rankings. The results are displayed in a review screen.
  • Invitation Emails: Organizers can send automated invitation emails to suggested matches. These emails include the project details and an optional custom comment from the organizer.
  • Database Migration: Included a Flask-Migrate script to add the ranking column to the users table.

This implementation avoids persisting the match suggestions directly, as requested, providing instead an immediately actionable workflow for organizers.

PR created automatically by Jules for task 2693533477962168735 started by @loleg

@google-labs-jules @loleg
Implement Teambuilder matching and project ranking
71ddf6f 
- Add _my_ranking field to User model for project preferences.
- Create SortableJS-based project ranking UI for participants.
- Implement Admin Teambuilder dashboard for organizers to view and match participants.
- Add email invitation system to notify matched participants with custom comments.
- Include database migration for the new User field.

Co-authored-by: loleg <31819+loleg@users.noreply.github.com>
@google-labs-jules
Copy link

google-labs-jules bot commented Feb 26, 2026

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

For security, I will only act on instructions from the user who triggered this task.

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@loleg