-
Feature
-
Resolution: Unresolved
-
Critical
-
None
-
False
-
None
-
False
-
Not Selected
-
0% To Do, 33% In Progress, 67% Done
Design Spec Doc is being finalized.
Original design separated Application list into different types, but most customers do not have tens of thousands of applications, so that design change would seem like a step backwards. It would also not necessarily solve the issues if any single type of application numbered in the tens of thousands. Seem child epics for new approach.
Feature Overview
We need to evaluate different options how we can improve performance when displaying Applications.
We might not add other types and we can think about adding a flag do restrict certain types like OpenShift Applications.
The current UI is designed for getting faster resource updates with small amounts of data but at the same time we sacrifice scalability and network efficiency.
Goals
we need to further improve the experience of customer with many Apps
We will closely work with GitopsOperator team
- ...
Requirements
This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.
| Requirement | Notes | isMvp? |
|---|---|---|
| CI - MUST be running successfully with test automation | This is a requirement for ALL features. |
YES |
| Release Technical Enablement | Provide necessary release enablement details and documents. |
YES |
(Optional) Use Cases
This Section:
- Main success scenarios - high-level user stories
- Alternate flow/scenarios - high-level user stories
- ...
Questions to answer
- ...
Out of Scope
- ...
Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?
Assumptions
- ...
Customer Considerations
- ...
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this
product feature? For users/admins? Other functions (security officers, etc)? - Does this feature have a doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content
Strategy. - What concepts do customers need to understand to be successful in
[action]? - How do we expect customers will use the feature? For what purpose(s)?
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical
Writer in writing the content? If yes, please link if available. - What is the doc impact (New Content, Updates to existing content, or
Release Note)?
