Skip to content

TBv3: filter chips show over the unfiltered tree in the Hierarchy view #2928

Open

Description

@paynejd

The Hierarchy view ignores facet filters (OpenConceptLab/oclweb3#68), but keeps them in the URL so Table and Card get them back. The header search bar reads filters from the URL and doesn't know which view is showing. So after a Table → Hierarchy switch, its filter chips (e.g. "Class: Diagnosis") sit over an unfiltered tree.

Acceptance criteria

  • In the Hierarchy view, the header search bar doesn't show list filters as applied, or shows them as not applying to the tree.
  • Switching back to Table or Card still restores the user's list filters.

Notes

  • Arriving in Hierarchy shows no chips: oclweb3#68 holds the saved defaults back until the first switch to Table or Card. The chips appear only after a round trip.
  • Probably needs the current view in the URL or in shared state, so the header can tell which view is showing.
  • Related, existing behavior: a search typed in the Hierarchy view returns flat search results, because the API's search path ignores onlyHierarchyRoot. Decide whether a search should switch the view to Table.

Activity

  1. added
    signal/low-riskSafe to execute with minimal downside
    signal/needs-humanA step only a person can take, such as a decision or sign-off
    signal/small-scopeLimited to a small part of the codebase
    signal/well-specifiedClear requirements and acceptance criteria
    on Oct 20, 2026
  2. ocl-automation commented on Oct 20, 2026

    @ocl-automation
    Collaborator

    Automated Triage — 2026-10-20

    Dimension Score
    Complexity 3
    Scope 2
    Clarity 4
    Dependency 2
    Risk 2

    Decision: decision/human-review
    Type: type/bug
    Signals: signal/low-risk, signal/small-scope, signal/well-specified, signal/needs-human
    Needs a person: decision: decide whether a search typed in the Hierarchy view should switch the view to Table

    The body describes the bug and gives two acceptance criteria. The fix is to make the header search bar aware of the current view, which likely means putting the view in the URL or shared state, and that touches a few files in the web app. It builds on oclweb3#68, which is open, but the existing behavior is enough to work against. The risk is low, since it is a UI display issue. The note on search-in-Hierarchy leaves a decision open, so I listed it as a human need.


    Generated by ticket-triage pipeline v3. Model: anthropic/claude-sonnet-5.5 (openrouter).

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

    component/webTermBrowser frontenddecision/human-reviewRequires human judgment or clarificationsignal/low-riskSafe to execute with minimal downsidesignal/needs-humanA step only a person can take, such as a decision or sign-offsignal/small-scopeLimited to a small part of the codebasesignal/well-specifiedClear requirements and acceptance criteriastage/triagedAI triage complete — scored and classifiedtype/bugSomething is broken

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions