XML

Word

Printable

Type: Epic
Resolution: Done
Priority: Major
Fix Version/s: ACM 2.15.0
Affects Version/s: None
Component/s: Application Lifecycle
Labels:
None

Epic Name:
Ensure Applicationsets in any namespace works
Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Color Status:
Not Selected
Epic Status:
To Do
Feature Link:
ACM-18916 - Applicationsets in any namespace GA
Parent Link:
ACM-18916Applicationsets in any namespace GA

SFDC Cases Links:
SFDC Cases Open:
SFDC Cases Counter:

PX Impact Score:

Intelligence Requested:
Market:

We need to focus on testing and identify usecases

Epic Goal

...

testing, document usecase restrictions

Why is this important?

...

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

...

Previous Work (Optional):

...

Open questions:

…

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 - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable.
Considerations were made for Extended Update Support (EUS)

duplicates

ACM-18207 ACM Need option to deploy to different namespaces (not only openshift-gitops) (TP)

Closed

Assignee:: Christian Stark

Reporter:: Christian Stark

QA Contact:: David Huynh

Votes:: 1 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2025/04/28 9:06 AM

Updated:: 2025/10/24 11:35 AM

Resolved:: 2025/10/24 11:35 AM