Five views
Grid, Kanban, Gantt, Calendar and Gallery.
QTable’s product roadmap spans two code repositories, but users experience one product capability set. GitHub Issues remains the detailed source of truth; this page keeps the layers clear.
The current main branches already cover the complete work shell and key service capabilities.
Grid, Kanban, Gantt, Calendar and Gallery.
Home / My Work / Projects Center.
Center, Workbench, server aggregation and public sharing.
Backend engine plus a real Automation Center and execution history.
Notifications, record collaboration, activity and realtime lifecycle.
Permission-aware global search, ChangeSet and Recycle Bin.
Goal planning, task planning, workload, assignment, Project Steward and safe action plans.
source tools / capture tools intake with source context and duplicate hints.
Stable S3-compatible object identity and permission-aware lifecycle.
QTable is the current open-source focus. Future capabilities will expand around data intake, automation, AI and higher-level work experiences, while the portal communicates durable product direction instead of binding the roadmap to specific GitHub issue numbers.
Multiple views, dashboards, collaboration, automation and AI workflows are delivered through the unified qtable-web experience.
Table / Record / View / Dashboard / Permission form one structured-work model shared by every experience and permission boundary.
qtable-server provides APIs, permissions, realtime collaboration, automation, audit, attachments, search, OAuth and AI services.
These are directional themes, not committed dates or claims that the capabilities have already shipped.
Continue strengthening end-to-end validation, large-table performance, realtime stability, responsive/accessibility quality, and self-host backup, restore and upgrade workflows.
Expand forms/public intake, APIs, webhooks, connectors and source intake so QTable can fit more naturally into existing business systems.
Extend BYO / self-hosted AI, permission-aware agents and automation orchestration while preserving the Preview → Confirm → Apply safety model.
Future higher-level QingZoneX experiences can reuse QTable structured data, permissions, collaboration and automation instead of creating a second data model.
It separates implemented capability, active hardening and future roadmap work.