Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

E2E: Fleet workspaces in namespace/project filtering #7470

Open
gaktive opened this issue Nov 16, 2022 · 2 comments
Open

E2E: Fleet workspaces in namespace/project filtering #7470

gaktive opened this issue Nov 16, 2022 · 2 comments
Labels
area/e2e area/fleet area/test Test (e2e and unit) kind/tech-debt Technical debt QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/3 Size Estimate 3
Milestone
v2.13.0

Comments

@gaktive
Copy link
Member

gaktive commented Nov 16, 2022 •
edited
Loading

Workspaces (Fleet - Continuous Delivery)

  • When a user selects a workspace in the top nav, then goes to the list view of a fleet resource such as Clusters, confirm that only resources in the selected namespaces are listed.
  • After refreshing the page, the namespace filter is still persisted.
  • Coming from an explorer page into Fleet, make sure workspace selected is still the the one picked earlier and also make sure it updates a list view properly (ex: Clusters)
  • Coming from Home into Fleet, make sure workspace selected is still the the one picked earlier and also make sure it updates a list view properly (ex: Clusters)
  • Coming from an explorer page (with refresh) into Fleet, make sure workspace selected is still the the one picked earlier and also make sure it updates a list view properly (ex: Clusters)
  • Coming from Home (with refresh) into Fleet, make sure workspace selected is still the the one picked earlier and also make sure it updates a list view properly (ex: Clusters)

(originally from #6613)
@gaktive gaktive added [zube]: Backlog kind/tech-debt Technical debt size/3 Size Estimate 3 labels Dec 1, 2022
@cnotv cnotv added this to the v2.7.next2 milestone May 15, 2023
@cnotv cnotv added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label May 15, 2023
@cnotv
Copy link
Contributor

cnotv commented May 15, 2023

@gaktive is this to be triaged or did we vote already?

@gaktive
Copy link
Member Author

gaktive commented May 15, 2023

@cnotv no voting happened yet. This was triaged in the past (December) and just waiting in the wings for an appropriate sprint to then groom.

@gaktive gaktive modified the milestones: v2.7.next2, v2.7.next3, v2.7.next4 Jun 5, 2023
@nwmac nwmac modified the milestones: v2.8.0, v2.8.next1 Aug 15, 2023
@Shavindra Shavindra self-assigned this Sep 6, 2023
@richard-cox richard-cox mentioned this issue Feb 14, 2024
Open
@nwmac nwmac modified the milestones: v2.9.0, v2.9.x Feb 27, 2024
@gaktive gaktive modified the milestones: v2.9.x, v2.12.0 Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/e2e area/fleet area/test Test (e2e and unit) kind/tech-debt Technical debt QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/3 Size Estimate 3
Projects
None yet
Milestone
v2.13.0
Development

No branches or pull requests
5 participants
@Shavindra @nwmac @cnotv @gaktive @richard-cox