Skip to content

[Tracking] Dashboard / UI issue triage #3828

Open

Description

@myasnikovdaniil

Scope

This issue is the single place to triage open Cozystack Console/dashboard work. The inventory was audited on 2026-08-14 by paginating all 416 open issues, all 174 open pull requests, every changed-file list, and cross-references from the resulting issues. It includes dashboard-owned work and cross-component defects whose body describes a concrete Console symptom or blocked Console workflow. Grafana dashboards, OpenSearch Dashboards, external application admin UIs, the website, and generic schema-backed application features are out of scope.

Definition of done

  • Reproduce every live bug against the current in-tree Console or record why reproduction is blocked.
  • Close confirmed duplicates and obsolete items left over from the standalone UI implementation.
  • Give every retained issue an accurate kind, area, triage state, and priority.
  • Link every active implementation PR and identify accepted issues that still have no owner or PR.
  • Keep this inventory synchronized until every listed item is closed or moved to a more specific tracker.

Open pull requests

Direct fixes and implementations

Mechanical PRs touching dashboard code

Issues currently labeled area/dashboard

Additional Console-impacting issues without area/dashboard

Related umbrella

#2733 tracks platform-wide error diagnostics; its concrete Console slice is already represented above by #3104 and should not be duplicated here.

Activity

  1. added
    epicA large development increment that brings definite value to Cozystack users
    priority/backlogGeneral backlog priority. Lower than priority/important-longterm
    kind/cleanupCategorizes issue or PR as related to cleanup of code, process, or technical debt
    triage/acceptedIndicates an issue is ready to be actively worked on
    area/dashboardIssues or PRs related to the dashboard / UI
    on Aug 14, 2026
  2. myasnikovdaniil commented on Aug 16, 2026

    @myasnikovdaniil
    ContributorAuthor

    State, 2026-08-16

    Worked the whole inventory. Nine of the listed issues needed no work at all, which is the headline: more than a third of this tracker was stale records rather than open defects.

    Closed, already fixed or not reproducing. #3101 and #3103 are unreachable on the shipped schemas: all 134 oneOf/anyOf/allOf are the int-or-string scalar pair with no properties, and none of the 16 shipped immutable paths contains a wildcard. #3104 is delivered by EventsTab.tsx, mounted at ApplicationDetailPage.tsx:206, which correlates Pods by both the application and the Helm label, PVCs both ways, and the HelmRelease. #3110 was fixed by bb322138e, #2174 by becf8d757, and #3114's 13 named packages are 9 absent from the vendored lockfile and 4 past every advisory. #3109 and #2845 do not reproduce: checked in a browser against a live cluster, the disks + add adds exactly one row on a fresh load and the dropdown populates immediately when the tenant has a VMDisk, and removing an array row leaves the remaining values attached to their own rows.

    Fixed in #3837, six of them: #3105 Ki-range sizes, #3106 tenant picker on /admin, #3107 403 on capacity drill-downs, #3102 immutable leaf under an absent ancestor, #3135 focus on a blocked submit, #3822 the tenant row not linking to its detail page.

    Worth recording from #3822, since the issue's framing was off: the tenant detail page exists and is complete, Delete and all six tabs included. Nothing in the list linked to it, because the name was plain text and the row's only link sat on the Edit button. Hence Edit then Cancel as the only way in.

    Reclassified, not console work. #3112 is a platform feature: no chart publishes a DNS name for an exposed Service except opensearch, and that one uses the internal cluster domain, so showing <service>.<host> would render a string that does not resolve. The suffix itself already exists and is already configurable, as the namespace label namespace.cozystack.io/host set from Tenant.spec.host in the tenant form. What is missing is publication, which is external-dns plus display rather than a UI change. #2909 is a packages/apps/vm-instance chart bug. #3096 is real and unfixed but lives in packages/k8s-client and needs a backoff design, so it wants its own pull request rather than the batch.

    Cross-component, still open and now with owners named. #3613 has one more instance, added there. #2853 needs packages/system/ingress-nginx values and the console Containerfile's nginx heredoc, neither of which has header buffers. #2678 needs packages/apps/mongodb plus packages/system/mongodb-rd, both defects reproduce. #2609 is backend before console. #3484 needs a live capture published to the website before the one-line README swap.

    New, found while working the list. The VMDisk form promises an in-page image upload that does not exist anywhere in the console. #3847 makes the promise true and hands over the virtctl command instead, because the browser cannot reach the CDI upload proxy on a stock cluster: the apiserver's services/proxy strips Authorization and the cdi-uploadproxy ingress uses ssl-passthrough, so CDI's internal certificate reaches the browser untrusted and with no matching SAN. Both measured against a live cluster.

    Pull requests listed here. #3115 and #3116 are rebased onto current main and pushed, #3115 with its two review findings fixed. #3795 is pushed. #2860, #2692, #3302 and #3363 are untouched.

    One architectural note that explains more than one entry above: SchemaForm binds ui:field: SourceField to the parent source object, and in RJSF a ui:field on a parent replaces rendering of the whole subtree, so the nested x-cozystack-options widget binding is silently dropped and a direct PVC read runs instead. The provider and the annotation both exist, so the mechanism looks wired and is not.

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

Metadata

Metadata

Labels

area/dashboardIssues or PRs related to the dashboard / UIepicA large development increment that brings definite value to Cozystack userskind/cleanupCategorizes issue or PR as related to cleanup of code, process, or technical debtpriority/backlogGeneral backlog priority. Lower than priority/important-longtermtriage/acceptedIndicates an issue is ready to be actively worked on

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions