Skip to content

Add per-admin hide of latest features nav bar list item #987

Closed

Description

@Bionic711

Each admin should be able to hide and show the latest features which will automatically reenabled when the system is updated. > store in user settings.
Each user should be able to hide and show the latest features which will automatically reenabled when the system is updated. > store in user settings.

Activity

  1. self-assigned this
    on Jul 2, 2026
  2. added theissue type on Jul 2, 2026
  3. moved this from Pending Evaluation to Scheduled in Simple Chat Roadmapon Jul 2, 2026
  4. paullizer commented on Jul 2, 2026

    @paullizer
    Contributor

    lol

  5. Bionic711 commented on Jul 20, 2026

    @Bionic711
    CollaboratorAuthor

    Implemented the versioned Latest Features navigation hide preference for this issue.

    Summary:

    • Added per-user latestFeaturesHiddenVersion support so Latest Features nav entries stay hidden only for the current app version.
    • Applied the hide behavior to both user-facing Support > Latest Features entries and the admin sidebar Admin Settings > Latest Features entry.
    • Added Profile Settings restore controls and local static JS for the ellipsis hide actions.
    • Added is_development=true as a development-only env override that hides the nav entries when explicitly true; unset/false/non-true values do not affect normal behavior.
    • Bumped the app version to v0.250.058 and added release notes.

    Validation:

    • Python compile passed for changed Python and test files.
    • node --check application/single_app/static/js/latest-features-nav.js passed.
    • Changed Jinja templates parsed successfully.
    • functional_tests/test_latest_features_nav_hide_preference.py passed.
    • functional_tests/test_admin_latest_features_tab.py passed.
    • functional_tests/test_latest_features_action_links.py passed.
    • ui_tests/test_latest_features_nav_hide_preference.py skipped cleanly when no authenticated Playwright storage state was configured.
    • git diff --check passed.
  6. Bionic711 commented on Jul 20, 2026

    @Bionic711
    CollaboratorAuthor

    PR-readiness update for the Latest Features navigation hide preference work.

    Summary:

    • Confirmed feature/hide_latest_features contains the latest origin/Development.
    • Aligned Latest Features test and release-note version markers with config.py version 0.250.059.
    • Added feature documentation at docs/explanation/features/LATEST_FEATURES_NAVIGATION_HIDE_PREFERENCE.md.
    • Committed cleanup locally as 783db97c docs: align latest features PR readiness assets.

    Validation passed:

    • git diff --check origin/Development...HEAD
    • git diff --check
    • Python compile check for application/single_app and changed tests
    • python scripts/check_swagger_routes.py for changed Python route/application files
    • Route policy inventory, unauthenticated policy contract, and route policy coverage tests
    • XSS changed-line sink scan
    • Broken access-control changed-line scan
    • node --check application/single_app/static/js/latest-features-nav.js
    • functional_tests/test_latest_features_action_links.py
    • functional_tests/test_latest_features_nav_hide_preference.py

    Skipped/gap:

    • ui_tests/test_latest_features_nav_hide_preference.py ran but skipped because local SIMPLECHAT_UI_BASE_URL and authenticated Playwright storage state were not configured.

    Security notes:

    • No changed paths matched .env, secret, token, session, connection-string, storage-key, or generated local artifact patterns.
    • Route decorator/policy, XSS, and broken-access-control checks passed.
  7. paullizer commented on Aug 19, 2026

    @paullizer
    Contributor

    Shipped in v0.250.059 via #1051.

    Release note entries:

    • v0.250.059: Versioned Latest Features Navigation Hide Preference

    Full notes: https://microsoft.github.io/simplechat/explanation/release_notes/

    Closing as completed. This issue stayed open after the fix merged because pull requests target Development while the repository default branch is main, so GitHub never applied the Fixes # keyword automatically.

  8. moved this from Scheduled to Released in Simple Chat Roadmapon Aug 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions