Skip to content

fix(invite): show org title instead of slug(org name) in member invite dropdown#1712

Open
Shreyag02 wants to merge 1 commit into
mainfrom
fix/invite-user-flow/org-name-mismatch
Open

fix(invite): show org title instead of slug(org name) in member invite dropdown#1712
Shreyag02 wants to merge 1 commit into
mainfrom
fix/invite-user-flow/org-name-mismatch

Conversation

@Shreyag02

Copy link
Copy Markdown

Summary

The organization dropdown in the admin "Invite user" flow rendered each org's URL slug (org.name) instead of its display title (org.title). Because the org list view and the invite email both use the title, the dropdown option didn't match what users saw elsewhere — selecting an org produced an invite email showing a different name.

Changes

  • Display org.title (with a fallback to org.name when title is unset) in the organization dropdown of the admin member-invite dialog.

Technical Details

In Frontier's org model, title is the human-readable display name while name is the URL slug / unique identifier. The invite dropdown in web/sdk/admin/views/users/list/invite-users.tsx was rendering org.name, whereas the org list (organizations/list/columns.tsx) and the invite email use org.title, causing the perceived mismatch. The submitted form value is still org.id, so only the visible label changed — the invite target is unaffected.

Test Plan

  • Manual testing completed
    • Open admin → Users → Invite user; confirm the organization dropdown labels match the names
      shown in the organization list.
    • Send an invite and verify the org name in the received email matches the selected dropdown
      option.
  • Build and type checking passes

SQL Safety (if your PR touches *_repository.go or goqu.*)

N/A — frontend-only change; no *_repository.go or goqu.* files touched.

@vercel

vercel Bot commented Jun 25, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
frontier Ready Ready Preview, Comment Jun 25, 2026 5:29pm

@coderabbitai

coderabbitai Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: e6ab1a5b-85f0-4c87-9e38-9425dcf0cba0

📥 Commits

Reviewing files that changed from the base of the PR and between 6dc16f9 and b36d8be.

📒 Files selected for processing (1)
  • web/sdk/admin/views/users/list/invite-users.tsx

📝 Walkthrough

Summary by CodeRabbit

  • Bug Fixes
    • Organization options in the user invite flow now show a more descriptive name when available, with a fallback to the previous label if needed.

Walkthrough

The invite-user organization dropdown now displays org.title when present and falls back to org.name.

Changes

Invite user organization label

Layer / File(s) Summary
Organization select label
web/sdk/admin/views/users/list/invite-users.tsx
The organization options render org.title when available and org.name otherwise.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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.

@coveralls

Copy link
Copy Markdown

Coverage Report for CI Build 28188569842

Coverage remained the same at 43.804%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 37058
Covered Lines: 16233
Line Coverage: 43.8%
Coverage Strength: 12.39 hits per line

💛 - Coveralls

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants