Skip to content

Should RI Exchange page honor Main Header global filter? (QA 2.9 -- design question) #871

Closed
Closed
Should RI Exchange page honor Main Header global filter? (QA 2.9 -- design question)#871
Labels
effort/mDaysimpact/manyAffects most userspriority/p3Polish / idea / may never shipseverity/lowMinor harmtriagedItem has been triagedtype/featNew capabilityurgency/this-sprintWithin the current sprint

Description

@cristim
cristim
opened on May 30, 2026

Question (QA Main Header 2.9)

Should the Inventory & Coverage > RI Exchange page honor the Main Header global Provider/Account chips?

QA filed 2.7+2.14 (Active Commitments) and 2.8+2.15 (Coverage) as bugs -- those should clearly respect the global filter. RI Exchange is more specialised (AWS-only workflow at present) and the QA tester wasn't sure whether the chip should apply.

Need product input:

  • If yes: same propagation pattern as the other sub-tabs (issue tracked under separate ticket).
  • If no: visually distinguish RI Exchange so it's clear the global filter doesn't apply (e.g. ghost-out the chip when on this tab, or a small "Not filtered" indicator).

Filed as type/question + status/needs-info.

Source

QA Main Header 2.9 (exploratory testing 2026-05-27).

Activity

  1. cristim
    added
    triagedItem has been triaged
    status/needs-infoAwaiting clarification from the asker
    priority/p3Polish / idea / may never ship
    type/questionQuestion for the project / asker
    type/featNew capability
    severity/lowMinor harm
    urgency/this-sprintWithin the current sprint
    impact/manyAffects most users
    effort/mDays
    and removed
    status/needs-infoAwaiting clarification from the asker
    type/questionQuestion for the project / asker
    on May 30, 2026

  2. cristim commented on Jun 1, 2026

    @cristim
    cristim
    on Jun 1, 2026
    MemberAuthor

    Decision: RI Exchange should honor the Main Header global Provider/Account filter, consistent with the other Inventory sub-tabs (Active Commitments + Coverage, #866/#881). RI Exchange is multi-provider (AWS exchangeable RIs + Azure exchangeable reservations; GCP has no RI-exchange concept). Behavior: Provider=AWS shows AWS RIs, Provider=Azure shows Azure reservations, Provider=GCP shows a 'not available for GCP' empty state; Account filter narrows to that account; provider-aware empty states throughout; clear any in-progress exchange selection when the filter changes. Converting from question to feat.

  3. cristim
    added a commit that references this issue on Jun 1, 2026

    feat(inventory/ri-exchange): honor Main Header global filter (closes #…

    73b3ac9

  4. cristim commented on Jun 1, 2026

    @cristim
    cristim
    on Jun 1, 2026
    MemberAuthor

    Resolved by PR #906 (merged 2026-06-01). RI Exchange now honors the Main Header global filter (AWS account-scoped + fail-closed, Azure subscription-scoped, GCP shows a 'not available' empty state) -- consistent with the other Inventory sub-tabs. Auto-close didn't fire because the PR merged to feat/multicloud-web-frontend, not the default branch. Closing manually.

  5. cristim
    closed this as completedon Jun 1, 2026
  6. cristim
    added a commit that references this issue on Jun 5, 2026

    docs(test): correct issue reference #871 -> #932 in ri-exchange Azure…

    1c76b95
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    effort/mDaysimpact/manyAffects most userspriority/p3Polish / idea / may never shipseverity/lowMinor harmtriagedItem has been triagedtype/featNew capabilityurgency/this-sprintWithin the current sprint

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions