lablup / lablup/backend.ai-webui
Expose every server-supported filter, ordering and field on super-admin list pages
- Dominant language
- TypeScript
- Stars
- 133
- Forks
- 81
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 355
Description
Super-admin list pages should expose every filter and ordering the manager already supports, and surface admin-relevant node fields that are fetched or available but never rendered.
Origin: Teams thread (UX Ideas) asking for a schedulable on/off filter on the agent list; the WebUI already had it, but a full audit found many gaps and several bugs.
Audit: `~/notes/admin-list-audit-20260914/SUMMARY.md` (per-page reports alongside).
Rules for every child issue:
- A filter/order that already existed at backend tag **26.4.0** is used unconditionally.
- Anything added after 26.4.0 is gated with `baiClient.supports(...)` (add the flag in `packages/backend.ai-client/src/client.ts` if missing).
- Every added filter/order is verified live against a manager (26.8.0rc1 test server) — the server must not error and results must change accordingly.
- One PR per page (or per tab group when a page is large), so each PR can be verified on one dev server page.
JIRA Issue: FR-3907
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with ~/notes/admin-list-audit-20260914/SUMMARY.md and its per-page reports to identify the affected super-admin list pages and their missing filters, ordering, and fields. Inspect packages/backend.ai-client/src/client.ts for required support flags, then verify each addition against the specified manager test server. Done means each page exposes its supported options without server errors and results change as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100