When adding a new user to a Workspace in Rally (Agile Central), a warning message appears indicating that the username you are trying to add conflicts with another username already in use.
Warning: The User could not be saved. Please correct the errors identified below and click one of the "Save" buttons.
Under the User Name, you see another error: "That User Name conflicts with <User>@<Company.com>
".
The error may also show as valueConflictsWithError
In Rally, all user names must be unique across all subscriptions. The user name is already associated within the subscription or another Rally subscription.
In Rally, all usernames must be unique across all subscriptions and be created using an email format, i.e. <User>@<Company.com>
They will need to contact the Subscription Administrator of the subscription with the existing username to request this change.
Ask the user to log in to their existing Rally account and change the username being used there.
They (or a Subscription Administrator) can do this by:
In every scenario, the best way to handle these issues is for a Subscription Administrator to update the conflicting account’s user name by adding a character (i.e. <User>@<Company.com>). This is because deleting a user account that may be tied to work items or other data in a subscription can break those linkages to that data. Changing the User ID in the subscription won't break the linkages.
However, in scenarios where the Subscription Administrator is unreachable, Support may be able to help by deleting the account. Again, this is not the preferred method as it can cause data issues. Below lists different scenarios:
If the user name already exists in an active Community/Starter Edition subscription, the user really does need to go to the Subscription Administrator who can update the user name. However, if there is proof that:
then with the direct user’s written request and this data for validation/supporting arguments, Support can delete the unused/conflicting account.
If the user name already exists in an inactive Community/Starter Edition subscription, Support can re-activate the subscription for a limited time so the Subscription Administrator can update the user name. However, there is proof that:
then with the direct user’s written request and this data for validation/supporting arguments, Support can delete the unused/conflicting account.
If the user name already exists in an active subscription for the same company, the Administrator and/or the user with the conflict will need to work with the Subscription Administrator for the conflicting account. Support can provide the Subscription Administrator contact information for same-company contacts only.
If the user name already exists in an expired trial or inactive subscription for the same company, the Administrator and/or the user with the conflict should attempt to work with the Subscription Administrator for the conflicting account. Support can share the Subscription Administrator contact information for same-company contacts only, and activate the subscription for 48 hours to allow for user name updates.
If the user name already exists in an expired Trial or subscription for the same company, and
then Support can delete the conflicting account.
If the user name already exists in an active subscription for a separate, other company, the user with the conflict will need to work with the Subscription Administrator for the conflicting account. Support cannot share the Subscription Administrator contact information for another company. That said, Support will reach out to the Subscription Administrator(s) of a separate company on the requestor’s behalf once via email.
In the event that the other company’s Subscription Administrator(s):
the Subscription Administrator with the user name conflict will need to choose a different user name. Support cannot delete the conflicting user account, send any further requests, or share any contact information.
**If the subscription is an inactive / expired subscription that is not Community/Starter Edition, Support cannot reach out to contact that Subscription Administrator. The Subscription Administrator with the user name conflict will need to choose a different user name.
keywords: login, password, unique, duplicate, valueConflictsWithError, unable to create account user,