Fix: Adding an organization to a user does not persist

[jmilljr24]

Edit a facilitator and add a new organization. The new organization should associated with the facilitator and display in their profile.

screenrecording-2026-01-16_20-12-46.mp4

[jimmynguyen]

Could I please be assigned to this issue?

[jimmynguyen]

@jmilljr24 It looks like there is a reject_if proc in the user model that requires the title to not be blank. However, the UI does not require the title field when adding an Organization Affiliation.

awbw/app/models/user.rb

Lines 45 to 46 in 55c2c07

	accepts_nested_attributes_for :project_users, allow_destroy: true,
	reject_if: proc { |attrs| attrs["project_id"].blank? || attrs["title"].blank? }

Could you please confirm whether or not the title field should be required?

When I update the reject_if proc in the user model to exclude the non-blank title validation, I am able to save the Organization Affiliation without defining a title.

Screen.Recording.2026-01-18.at.12.54.48.AM.mov

[maebeale]

wow, eagle eyes @jimmynguyen! yes, it should be required. so appreciate your thoroughness!

[jimmynguyen]

Do you have any suggestion on the best way to enforce validation?

My initial thought was to add a validates_presence_of :title on the project_user model, but it looks like that only adds an asterisk next to the Title label in the UI.

awbw/app/models/project_user.rb

Lines 1 to 6 in dfa4ae8

	class ProjectUser < ApplicationRecord
	belongs_to :project
	belongs_to :user
	# Validations
	validates_presence_of :project_id

When I click Submit, it looks like the entry is just ignored silently like it is now instead of "loudly".

[jmilljr24]

@jimmynguyen if you push up a draft PR I can take a deeper look but my first thought would be to see if we can accomplish the validations without using reject_if at all.