Epic Goal

• Remove requirement that email addresses are unique across organizations

Why is this important?

• Users tend to have a single email email address but many organizations. They currently cannot have all those organizations email their single address. This causes them additional burden of creating and managing multiple email addresses if they wish to receive all notifications from all their orgs

Scenarios

1. A user can create an organization with an email address and can then create another organization using the same email address
2. An organization can be updated to use an email address already registered to another organization

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions::

1. Are there any hard checks or assumptions in the code related to the uniqueness of an org email address?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>