-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
Handle email integrations like other communication integrations
-
Future Sustainability
-
False
-
-
False
-
Unset
-
To Do
-
75% To Do, 0% In Progress, 25% Done
-
-
-
Summary and goal
Currently email integrations are not directly visible from UI, but they are grom API. We would lmike to make those visible from UI like other communication integration types.
Issues to address:
- Many integration types were created by the application itself for technical purpose, those integrations doesn't make sense anymore and must be removed before exposing Email integrations into UI
- The legacy solution create one email integration for each associated RBAC group, those integrations must be grouped into a single one with multiple linked RBAC groups
- Email integrations have a name based on a UUID, they should be renamed
Acceptance Criteria
These conditions must be met for the epic to be considered complete. This provides a detailed definition of scope and the expected outcomes, written from a user's point of view.
Checklist
| Checklist Item | Required | Notes or Comments |
|---|---|---|
| Workstream or external team dependencies? | Y / N | |
ADR Required?
|
Y / N | |
Testing plans
|
Y / N | |
Known dependencies?
|
Y / N |
Open Questions
Capture any open questions and resolutions related to the epic goal or acceptance criteria. Add any additional details, questions or decisions that need to be made or addressed.