You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When saving a User object, we want to make sure we can't have the scenario where a user has a portfolio but no role. Our goal is to display the roles for each user with the bare minimum being an org member. Likewise, ti wouldn't make sense to have a portfolio role with no portfolio in the object.
Acceptance criteria
On the User table, portfolio roles and portfolio must be both filled in or both empty when a user object is saved, otherwise an error occurs
for instance, you cannot have portfolio roles filled in but leave portfolio blank. Likewise, if portfolio field is filled in roles is blank then a validation error occurs.
Issue description
When saving a User object, we want to make sure we can't have the scenario where a user has a portfolio but no role. Our goal is to display the roles for each user with the bare minimum being an org member. Likewise, ti wouldn't make sense to have a portfolio role with no portfolio in the object.
Acceptance criteria
Additional context
No response
Links to other issues
blocks #2402
The text was updated successfully, but these errors were encountered: