Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix error handling on Add New Member form when the user already belongs to the portfolio #3528

Open
rachidatecs opened this issue Feb 14, 2025 · 0 comments
Labels
bug Something that isn't working as intended dev issue is for the dev team

Comments

@rachidatecs
Copy link
Contributor

rachidatecs commented Feb 14, 2025

Current Behavior

The current error is:
"This user is already assigned to a portfolio. Based on current waffle flag settings, users cannot be assigned to multiple portfolios." (in the case of a user)

Or
"This user is already assigned to a portfolio invitation. Based on current waffle flag settings, users cannot be assigned to multiple portfolios." (in the case of a non-user)

Expected Behavior

The errors should be:
"< email > is already a member of another .gov organization." (in the case of a user)

Or
"< email > has already been invited to another .gov organization." (in the case of a non-user)

These errors should trigger regardless of the multiple_portfolio flag setting

Steps to Reproduce

  1. Invite an existing portfolio user to the portfolio
  2. Invite an already invited non-user email to the portfolio

Environment

No response

Additional Context

No response

Issue Links

No response

@rachidatecs rachidatecs added the bug Something that isn't working as intended label Feb 14, 2025
@allly-b allly-b added the dev issue is for the dev team label Feb 18, 2025
@allly-b allly-b moved this from 👶 New to 🍦 Backlog in .gov Product Board Feb 18, 2025
@allly-b allly-b moved this from 🍦 Backlog to 🎯 Ready in .gov Product Board Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that isn't working as intended dev issue is for the dev team
Projects
Status: 🎯 Ready
Development

No branches or pull requests

2 participants