-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
Notifications and integration cleanup
-
False
-
-
False
-
Unset
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
-
Review the CRCPLAN parent feature for additional context, including the feature overview, goals, user stories and use cases, acceptance criteria, designs, dependencies, risks, assumptions, pending questions and documentation callouts.
Summary and goal
With all of the recent changes to integration and notifications we should have to cleanup the code slightly not to cause any extra problems when adding new features to it.
Acceptance Criteria
With the cleanup there are 4 rather large milestones we can work on them in parallel:
- There are no feature flags related to sources + integrations work
- Wording update based on doc https://docs.google.com/document/d/1XFEGABMV1h7vBa4-xtDZITswn9zIGjg4xec9gwt40y8/edit
- Move integration pages to sources UI repository (will be handled in Q1 Tech Debt)
- Move behavior group machine to machine creation as a seperate step when creating new integration - RHCLOUD-30318
Checklist
Checklist Item | Required | Notes or Comments |
---|---|---|
Workstream or external team dependencies? | N | |
ADR Required?
|
N | |
Testing plans
|
N | Regression tests should not break because we shouldn't be changing the UI to great extend. |
Known dependencies?
|
N |
Open Questions
None
- is related to
-
RHCLOUD-30318 Move behavior group machine to machine creation as a separate step when creating new integration
- In Progress
- mentioned in
-
Page Loading...