Loading...

XML

Word

Printable

Type: Epic
Resolution: Unresolved
Priority: Undefined
Fix Version/s: None
Affects Version/s: None
Component/s: DevConsole Integration (UI/Backend), Operator
Labels:
- ArgoRollouts

Epic Name:
Progressive Delivery in OpenShift Console's Topology View
Blocked:
False
Blocked Reason:
None
Ready:
False
Epic Status:
To Do
Feature Link:
SECFLOWOTL-163 - Progressive Delivery in OpenShift Console's Topology View
Hierarchy Progress:
0
Hierarchy Progress Bar:

0% 0%
Intelligence Requested:
Market:

SFDC Cases Links:
SFDC Cases Counter:

Epic Goal

(Much of the details are TBD until the child spike is completed)
...

Jonathan: I converted this from a spike to a feature, based on discussions with architect/PM. The original spike can be found as a child of the epic: https://issues.redhat.com/browse/GITOPS-2339. Much of the details are TBD until the spike is completed.

Why is this important?

Scenarios

Acceptance Criteria (Mandatory)

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

Dependencies (internal and external)

Previous Work (Optional):

Open questions::

Done Checklist

Acceptance criteria are met
Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
User Journey automation is delivered
Support and SRE teams are provided with enough skills to support the feature in production environment

Assignee:: Unassigned

Reporter:: Jonathan West

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2024/04/24 10:57 PM

Updated:: 2024/04/24 11:04 PM

Details

Description

Epic Goal

Why is this important?

Scenarios

Acceptance Criteria (Mandatory)

Dependencies (internal and external)

Previous Work (Optional):

Open questions::

Done Checklist

Attachments

Activity

People

Dates