Kanban, gantt and timeline lenses over the same task data#49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-warren merged 2 commits into from
Sep 1, 2026
Merged

Kanban, gantt and timeline lenses over the same task data #49

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7099555
Add board, schedule, recent, by_unit and catalog_tree lenses
os-warren Sep 1, 2026
997782a
Add test/views.test.ts — binding, field-reference and nav-reachabilit…
os-warren Sep 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions src/apps/duly.app.ts
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -28,6 +28,12 @@ export const DulyApp = App.create({
{ id: 'nav_my_duties', type: 'object', objectName: 'duly_duty', viewName: 'mine', label: 'My duties', icon: 'clipboard-list' },
{ id: 'nav_standing', type: 'object', objectName: 'duly_duty', viewName: 'standing', label: 'Standing duties', icon: 'anchor' },
{ id: 'nav_log', type: 'object', objectName: 'duly_log_entry', label: 'Work log', icon: 'notebook-pen' },
// The board lives HERE, not under Team, and that placement is a
// product rule rather than taste: dragging a card writes `status`, and
// managers do not enter status — assigning is their only write. A
// drag-to-done surface in the manager's section would invite exactly
// the write the model refuses them.
{ id: 'nav_board', type: 'object', objectName: 'duly_task', viewName: 'board', label: 'Board', icon: 'kanban' },
],
},
{
Expand All@@ -39,6 +45,9 @@ export const DulyApp = App.create({
{ id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
{ id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
{ id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
{ id: 'nav_schedule', type: 'object', objectName: 'duly_task', viewName: 'schedule', label: 'Schedule', icon: 'gantt-chart' },
{ id: 'nav_recent', type: 'object', objectName: 'duly_task', viewName: 'recent', label: 'Recent activity', icon: 'history' },
{ id: 'nav_by_unit', type: 'object', objectName: 'duly_task', viewName: 'by_unit', label: 'By business unit', icon: 'building-2' },
],
},
{
Expand All@@ -49,6 +58,7 @@ export const DulyApp = App.create({
children: [
{ id: 'nav_catalog', type: 'object', objectName: 'duly_catalog_item', label: 'Role catalog', icon: 'list-checks' },
{ id: 'nav_all_duties', type: 'object', objectName: 'duly_duty', label: 'All duties', icon: 'library' },
{ id: 'nav_catalog_tree', type: 'object', objectName: 'duly_duty', viewName: 'catalog_tree', label: 'What each team owes', icon: 'folder-tree' },
],
},
],
Expand Down
42 changes: 42 additions & 0 deletions src/views/duty.view.ts
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -43,5 +43,47 @@ export const DutyViews = defineView({
columns: [{ field: 'name' }, { field: 'owner' }, { field: 'business_unit' }, { field: 'status' }],
filter: [{ field: 'form', operator: 'equals', value: 'standing' }],
},

/**
* "What does this team owe" — every duty bucketed by business unit, then
* by the one accountable person inside it, both levels collapsible.
*
* ⚠️ DELIBERATELY `type: 'grid'` + `grouping`, NOT `type: 'tree'`, and the
* difference is not cosmetic. The platform's `tree` view is a
* SELF-REFERENCING hierarchy: `TreeConfigSchema` takes a `parentField`
* single-parent pointer, and the renderer nests a record under another
* record of the SAME object by matching `record[parentField]` against the
* sibling ids. `duly_duty` has no self-reference — its lookups point at
* `sys_business_unit`, `duly_catalog_item` and a user — so a `type: 'tree'`
* view here resolves no parent for any row, puts every duty at depth 0 and
* renders a FLAT list. The renderer never reads `grouping`, so declaring
* the two levels alongside it would change nothing, and nothing in
* `pnpm validate` says so: the `view/layout-without-binding` gate does not
* cover `tree` at all. That is the exact "renders wrong while authoring
* reports success" shape this app's views exist to avoid, so it is not
* shipped and the gap is filed upstream instead (see the PR body).
*
* The grid's grouping hook is the honest expression of the same idea and
* it is measured, not assumed: it recurses through `grouping.fields`,
* building nested `subgroups` with per-level collapse — a real two-level
* hierarchy. Group keys sort by LABEL, never by bucket size, so no team
* and no person is ever ordered by how much they owe.
*/
catalog_tree: {
label: 'What each team owes',
type: 'grid',
data,
columns: [
{ field: 'name' },
{ field: 'form' },
{ field: 'frequency' },
{ field: 'source' },
{ field: 'status' },
],
grouping: {
fields: [{ field: 'business_unit' }, { field: 'owner' }],
},
sort: [{ field: 'name', order: 'asc' }],
},
},
});
131 changes: 131 additions & 0 deletions src/views/task.view.ts
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -161,5 +161,136 @@ export const TaskViews = defineView({
},
sort: [{ field: 'due_date', order: 'asc' }],
},

/**
* Kanban. Columns come from `duly_task.status` — the renderer reads the
* field's own `options` for the column set, their order and their labels
* (measured in the console's `plugin-kanban`), so the board cannot drift
* from the object.
*
* Dragging a card writes ONE field. Measured against the renderer's move
* handler: `dataSource.update(object, id, { [groupBy]: toColumnId })` —
* `status` and nothing else, which is the same write the row action does.
* It is NOT gated on `inlineEdit`; it is gated on update permission, so a
* user who may not write `status` gets the platform's rejection rather
* than a silent no-op.
*
* `inlineEdit` is still declared, and it is not decoration: the toolbar
* lets a viewer switch this view to its grid visualisation, and the
* adapter honours `inlineEdit` on that branch (`editable:` is set in the
* grid case only). On the kanban branch itself it is inert.
*
* No `summarizeField`: it renders a per-column SUM, and there is no number
* on a task worth totalling. The nearest candidate would be a count, and
* counts are never ranked or compared here.
*/
board: {
label: 'Board',
type: 'kanban',
data,
columns: [{ field: 'subject' }, { field: 'due_date' }, { field: 'owner' }, { field: 'source' }],
kanban: {
groupByField: 'status',
// The card face, in reading order: what it is, when it is owed, whose
// it is, and where it came from.
columns: ['subject', 'due_date', 'owner', 'source'],
},
inlineEdit: true,
sort: [{ field: 'due_date', order: 'asc' }],
},

/**
* Gantt. The bar runs `visible_from` → `due_date`, and that span IS the
* lead time: a bar that starts on its own due date is a task that first
* appeared the day it was already owed, which is a report on a failure
* rather than a reminder. `lead_days` on the duty is what produces the
* length, and this is the only screen where you can see it.
*
* Grouped by owner so an overloaded fortnight is visible as one person's
* row going solid, before the period arrives.
*
* The filter is not a scope narrowing, it is a correctness one: the
* renderer maps a missing date to `new Date()`, so an undated one-off
* would draw a zero-width bar on TODAY and read as load that does not
* exist. Both columns are stored and indexed; the unary operators carry
* their direction in the name and take no value.
*
* No `colorField`, deliberately, and this is measured rather than an
* oversight: the gantt renderer passes `record[colorField]` straight into
* `backgroundColor`, so `colorField: 'status'` sets `background: "open"` —
* not a colour, silently dropped, every bar identical. With the key
* ABSENT the same renderer falls through to its status-derived palette and
* the bars separate by state. Filed upstream; see the PR body.
*/
schedule: {
label: 'Schedule',
type: 'gantt',
data,
columns: [
{ field: 'subject' },
{ field: 'status' },
{ field: 'owner' },
{ field: 'visible_from' },
{ field: 'due_date' },
],
gantt: {
startDateField: 'visible_from',
endDateField: 'due_date',
titleField: 'subject',
groupByField: 'owner',
viewMode: 'week',
tooltipFields: [{ field: 'status' }, { field: 'period_key' }, { field: 'source' }],
},
filter: [
{ field: 'visible_from', operator: 'is_not_null' },
{ field: 'due_date', operator: 'is_not_null' },
],
sort: [{ field: 'visible_from', order: 'asc' }],
},

/**
* Timeline — the visual companion to `stalled`. Ordered by
* `last_update_at`, which `task.hook.ts` stamps on a status change or a
* note edit and deliberately does NOT advance on an administrative write,
* so this really is "what has been happening" and not "what has been
* touched".
*
* `colorField` earns its place here: the timeline renderer resolves it
* against the object's own `status` options and uses the AUTHORED colours
* (`#35674D` for done, and so on), so this lens and the status badge in
* every grid read the same.
*/
recent: {
label: 'Recent activity',
type: 'timeline',
data,
columns: [{ field: 'subject' }, { field: 'status' }, { field: 'owner' }, { field: 'last_update_at' }],
timeline: {
startDateField: 'last_update_at',
titleField: 'subject',
colorField: 'status',
scale: 'day',
},
sort: [{ field: 'last_update_at', order: 'desc' }],
},

/**
* The same rows a manager already reads, bucketed by team. `business_unit`
* is denormalised onto the task at dispatch precisely so a rollup like
* this survives a later transfer.
*
* Groups sort by LABEL — measured in the grid's grouping hook, which sorts
* group keys with a locale compare on the label and never on the bucket
* size. Nothing here ranks a unit, or a person, by a count.
*/
by_unit: {
label: 'By business unit',
type: 'grid',
data,
columns,
grouping: { fields: [{ field: 'business_unit' }] },
bulkActionDefs: bulkActions,
sort: [{ field: 'due_date', order: 'asc' }],
},
},
});
Loading
Loading
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
Kanban, gantt and timeline lenses over the same task data#49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026
 Merged


Kanban, gantt and timeline lenses over the same task data
#49
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
7099555

Add board, schedule, recent, by_unit and catalog_tree lenses


os-warren Sep 1, 2026
997782a

Add test/views.test.ts — binding, field-reference and nav-reachabilit…


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


10 changes: 10 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -28,6 +28,12 @@ export const DulyApp = App.create({
 { id: 'nav_my_duties', type: 'object', objectName: 'duly_duty', viewName: 'mine', label: 'My duties', icon: 'clipboard-list' },
 { id: 'nav_standing', type: 'object', objectName: 'duly_duty', viewName: 'standing', label: 'Standing duties', icon: 'anchor' },
 { id: 'nav_log', type: 'object', objectName: 'duly_log_entry', label: 'Work log', icon: 'notebook-pen' },
 // The board lives HERE, not under Team, and that placement is a
 // product rule rather than taste: dragging a card writes `status`, and
 // managers do not enter status — assigning is their only write. A
 // drag-to-done surface in the manager's section would invite exactly
 // the write the model refuses them.
 { id: 'nav_board', type: 'object', objectName: 'duly_task', viewName: 'board', label: 'Board', icon: 'kanban' },
 ],
 },
 {
Expand All@@ -39,6 +45,9 @@ export const DulyApp = App.create({
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
 { id: 'nav_schedule', type: 'object', objectName: 'duly_task', viewName: 'schedule', label: 'Schedule', icon: 'gantt-chart' },
 { id: 'nav_recent', type: 'object', objectName: 'duly_task', viewName: 'recent', label: 'Recent activity', icon: 'history' },
 { id: 'nav_by_unit', type: 'object', objectName: 'duly_task', viewName: 'by_unit', label: 'By business unit', icon: 'building-2' },
 ],
 },
 {
Expand All@@ -49,6 +58,7 @@ export const DulyApp = App.create({
 children: [
 { id: 'nav_catalog', type: 'object', objectName: 'duly_catalog_item', label: 'Role catalog', icon: 'list-checks' },
 { id: 'nav_all_duties', type: 'object', objectName: 'duly_duty', label: 'All duties', icon: 'library' },
 { id: 'nav_catalog_tree', type: 'object', objectName: 'duly_duty', viewName: 'catalog_tree', label: 'What each team owes', icon: 'folder-tree' },
 ],
 },
 ],
Expand Down

42 changes: 42 additions & 0 deletions
src/views/duty.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -43,5 +43,47 @@ export const DutyViews = defineView({
 columns: [{ field: 'name' }, { field: 'owner' }, { field: 'business_unit' }, { field: 'status' }],
 filter: [{ field: 'form', operator: 'equals', value: 'standing' }],
 },

 /**
 * "What does this team owe" — every duty bucketed by business unit, then
 * by the one accountable person inside it, both levels collapsible.
 *
 * ⚠️ DELIBERATELY `type: 'grid'` + `grouping`, NOT `type: 'tree'`, and the
 * difference is not cosmetic. The platform's `tree` view is a
 * SELF-REFERENCING hierarchy: `TreeConfigSchema` takes a `parentField`
 * single-parent pointer, and the renderer nests a record under another
 * record of the SAME object by matching `record[parentField]` against the
 * sibling ids. `duly_duty` has no self-reference — its lookups point at
 * `sys_business_unit`, `duly_catalog_item` and a user — so a `type: 'tree'`
 * view here resolves no parent for any row, puts every duty at depth 0 and
 * renders a FLAT list. The renderer never reads `grouping`, so declaring
 * the two levels alongside it would change nothing, and nothing in
 * `pnpm validate` says so: the `view/layout-without-binding` gate does not
 * cover `tree` at all. That is the exact "renders wrong while authoring
 * reports success" shape this app's views exist to avoid, so it is not
 * shipped and the gap is filed upstream instead (see the PR body).
 *
 * The grid's grouping hook is the honest expression of the same idea and
 * it is measured, not assumed: it recurses through `grouping.fields`,
 * building nested `subgroups` with per-level collapse — a real two-level
 * hierarchy. Group keys sort by LABEL, never by bucket size, so no team
 * and no person is ever ordered by how much they owe.
 */
 catalog_tree: {
 label: 'What each team owes',
 type: 'grid',
 data,
 columns: [
 { field: 'name' },
 { field: 'form' },
 { field: 'frequency' },
 { field: 'source' },
 { field: 'status' },
 ],
 grouping: {
 fields: [{ field: 'business_unit' }, { field: 'owner' }],
 },
 sort: [{ field: 'name', order: 'asc' }],
 },
 },
});

131 changes: 131 additions & 0 deletions
src/views/task.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -161,5 +161,136 @@ export const TaskViews = defineView({
 },
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Kanban. Columns come from `duly_task.status` — the renderer reads the
 * field's own `options` for the column set, their order and their labels
 * (measured in the console's `plugin-kanban`), so the board cannot drift
 * from the object.
 *
 * Dragging a card writes ONE field. Measured against the renderer's move
 * handler: `dataSource.update(object, id, { [groupBy]: toColumnId })` —
 * `status` and nothing else, which is the same write the row action does.
 * It is NOT gated on `inlineEdit`; it is gated on update permission, so a
 * user who may not write `status` gets the platform's rejection rather
 * than a silent no-op.
 *
 * `inlineEdit` is still declared, and it is not decoration: the toolbar
 * lets a viewer switch this view to its grid visualisation, and the
 * adapter honours `inlineEdit` on that branch (`editable:` is set in the
 * grid case only). On the kanban branch itself it is inert.
 *
 * No `summarizeField`: it renders a per-column SUM, and there is no number
 * on a task worth totalling. The nearest candidate would be a count, and
 * counts are never ranked or compared here.
 */
 board: {
 label: 'Board',
 type: 'kanban',
 data,
 columns: [{ field: 'subject' }, { field: 'due_date' }, { field: 'owner' }, { field: 'source' }],
 kanban: {
 groupByField: 'status',
 // The card face, in reading order: what it is, when it is owed, whose
 // it is, and where it came from.
 columns: ['subject', 'due_date', 'owner', 'source'],
 },
 inlineEdit: true,
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Gantt. The bar runs `visible_from` → `due_date`, and that span IS the
 * lead time: a bar that starts on its own due date is a task that first
 * appeared the day it was already owed, which is a report on a failure
 * rather than a reminder. `lead_days` on the duty is what produces the
 * length, and this is the only screen where you can see it.
 *
 * Grouped by owner so an overloaded fortnight is visible as one person's
 * row going solid, before the period arrives.
 *
 * The filter is not a scope narrowing, it is a correctness one: the
 * renderer maps a missing date to `new Date()`, so an undated one-off
 * would draw a zero-width bar on TODAY and read as load that does not
 * exist. Both columns are stored and indexed; the unary operators carry
 * their direction in the name and take no value.
 *
 * No `colorField`, deliberately, and this is measured rather than an
 * oversight: the gantt renderer passes `record[colorField]` straight into
 * `backgroundColor`, so `colorField: 'status'` sets `background: "open"` —
 * not a colour, silently dropped, every bar identical. With the key
 * ABSENT the same renderer falls through to its status-derived palette and
 * the bars separate by state. Filed upstream; see the PR body.
 */
 schedule: {
 label: 'Schedule',
 type: 'gantt',
 data,
 columns: [
 { field: 'subject' },
 { field: 'status' },
 { field: 'owner' },
 { field: 'visible_from' },
 { field: 'due_date' },
 ],
 gantt: {
 startDateField: 'visible_from',
 endDateField: 'due_date',
 titleField: 'subject',
 groupByField: 'owner',
 viewMode: 'week',
 tooltipFields: [{ field: 'status' }, { field: 'period_key' }, { field: 'source' }],
 },
 filter: [
 { field: 'visible_from', operator: 'is_not_null' },
 { field: 'due_date', operator: 'is_not_null' },
 ],
 sort: [{ field: 'visible_from', order: 'asc' }],
 },

 /**
 * Timeline — the visual companion to `stalled`. Ordered by
 * `last_update_at`, which `task.hook.ts` stamps on a status change or a
 * note edit and deliberately does NOT advance on an administrative write,
 * so this really is "what has been happening" and not "what has been
 * touched".
 *
 * `colorField` earns its place here: the timeline renderer resolves it
 * against the object's own `status` options and uses the AUTHORED colours
 * (`#35674D` for done, and so on), so this lens and the status badge in
 * every grid read the same.
 */
 recent: {
 label: 'Recent activity',
 type: 'timeline',
 data,
 columns: [{ field: 'subject' }, { field: 'status' }, { field: 'owner' }, { field: 'last_update_at' }],
 timeline: {
 startDateField: 'last_update_at',
 titleField: 'subject',
 colorField: 'status',
 scale: 'day',
 },
 sort: [{ field: 'last_update_at', order: 'desc' }],
 },

 /**
 * The same rows a manager already reads, bucketed by team. `business_unit`
 * is denormalised onto the task at dispatch precisely so a rollup like
 * this survives a later transfer.
 *
 * Groups sort by LABEL — measured in the grid's grouping hook, which sorts
 * group keys with a locale compare on the label and never on the bucket
 * size. Nothing here ranks a unit, or a person, by a count.
 */
 by_unit: {
 label: 'By business unit',
 type: 'grid',
 data,
 columns,
 grouping: { fields: [{ field: 'business_unit' }] },
 bulkActionDefs: bulkActions,
 sort: [{ field: 'due_date', order: 'asc' }],
 },
 },
});
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Kanban, gantt and timeline lenses over the same task data#49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026
 Merged


Kanban, gantt and timeline lenses over the same task data
#49
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
7099555

Add board, schedule, recent, by_unit and catalog_tree lenses


os-warren Sep 1, 2026
997782a

Add test/views.test.ts — binding, field-reference and nav-reachabilit…


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


10 changes: 10 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -28,6 +28,12 @@ export const DulyApp = App.create({
 { id: 'nav_my_duties', type: 'object', objectName: 'duly_duty', viewName: 'mine', label: 'My duties', icon: 'clipboard-list' },
 { id: 'nav_standing', type: 'object', objectName: 'duly_duty', viewName: 'standing', label: 'Standing duties', icon: 'anchor' },
 { id: 'nav_log', type: 'object', objectName: 'duly_log_entry', label: 'Work log', icon: 'notebook-pen' },
 // The board lives HERE, not under Team, and that placement is a
 // product rule rather than taste: dragging a card writes `status`, and
 // managers do not enter status — assigning is their only write. A
 // drag-to-done surface in the manager's section would invite exactly
 // the write the model refuses them.
 { id: 'nav_board', type: 'object', objectName: 'duly_task', viewName: 'board', label: 'Board', icon: 'kanban' },
 ],
 },
 {
Expand All@@ -39,6 +45,9 @@ export const DulyApp = App.create({
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
 { id: 'nav_schedule', type: 'object', objectName: 'duly_task', viewName: 'schedule', label: 'Schedule', icon: 'gantt-chart' },
 { id: 'nav_recent', type: 'object', objectName: 'duly_task', viewName: 'recent', label: 'Recent activity', icon: 'history' },
 { id: 'nav_by_unit', type: 'object', objectName: 'duly_task', viewName: 'by_unit', label: 'By business unit', icon: 'building-2' },
 ],
 },
 {
Expand All@@ -49,6 +58,7 @@ export const DulyApp = App.create({
 children: [
 { id: 'nav_catalog', type: 'object', objectName: 'duly_catalog_item', label: 'Role catalog', icon: 'list-checks' },
 { id: 'nav_all_duties', type: 'object', objectName: 'duly_duty', label: 'All duties', icon: 'library' },
 { id: 'nav_catalog_tree', type: 'object', objectName: 'duly_duty', viewName: 'catalog_tree', label: 'What each team owes', icon: 'folder-tree' },
 ],
 },
 ],
Expand Down

42 changes: 42 additions & 0 deletions
src/views/duty.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -43,5 +43,47 @@ export const DutyViews = defineView({
 columns: [{ field: 'name' }, { field: 'owner' }, { field: 'business_unit' }, { field: 'status' }],
 filter: [{ field: 'form', operator: 'equals', value: 'standing' }],
 },

 /**
 * "What does this team owe" — every duty bucketed by business unit, then
 * by the one accountable person inside it, both levels collapsible.
 *
 * ⚠️ DELIBERATELY `type: 'grid'` + `grouping`, NOT `type: 'tree'`, and the
 * difference is not cosmetic. The platform's `tree` view is a
 * SELF-REFERENCING hierarchy: `TreeConfigSchema` takes a `parentField`
 * single-parent pointer, and the renderer nests a record under another
 * record of the SAME object by matching `record[parentField]` against the
 * sibling ids. `duly_duty` has no self-reference — its lookups point at
 * `sys_business_unit`, `duly_catalog_item` and a user — so a `type: 'tree'`
 * view here resolves no parent for any row, puts every duty at depth 0 and
 * renders a FLAT list. The renderer never reads `grouping`, so declaring
 * the two levels alongside it would change nothing, and nothing in
 * `pnpm validate` says so: the `view/layout-without-binding` gate does not
 * cover `tree` at all. That is the exact "renders wrong while authoring
 * reports success" shape this app's views exist to avoid, so it is not
 * shipped and the gap is filed upstream instead (see the PR body).
 *
 * The grid's grouping hook is the honest expression of the same idea and
 * it is measured, not assumed: it recurses through `grouping.fields`,
 * building nested `subgroups` with per-level collapse — a real two-level
 * hierarchy. Group keys sort by LABEL, never by bucket size, so no team
 * and no person is ever ordered by how much they owe.
 */
 catalog_tree: {
 label: 'What each team owes',
 type: 'grid',
 data,
 columns: [
 { field: 'name' },
 { field: 'form' },
 { field: 'frequency' },
 { field: 'source' },
 { field: 'status' },
 ],
 grouping: {
 fields: [{ field: 'business_unit' }, { field: 'owner' }],
 },
 sort: [{ field: 'name', order: 'asc' }],
 },
 },
});

131 changes: 131 additions & 0 deletions
src/views/task.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -161,5 +161,136 @@ export const TaskViews = defineView({
 },
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Kanban. Columns come from `duly_task.status` — the renderer reads the
 * field's own `options` for the column set, their order and their labels
 * (measured in the console's `plugin-kanban`), so the board cannot drift
 * from the object.
 *
 * Dragging a card writes ONE field. Measured against the renderer's move
 * handler: `dataSource.update(object, id, { [groupBy]: toColumnId })` —
 * `status` and nothing else, which is the same write the row action does.
 * It is NOT gated on `inlineEdit`; it is gated on update permission, so a
 * user who may not write `status` gets the platform's rejection rather
 * than a silent no-op.
 *
 * `inlineEdit` is still declared, and it is not decoration: the toolbar
 * lets a viewer switch this view to its grid visualisation, and the
 * adapter honours `inlineEdit` on that branch (`editable:` is set in the
 * grid case only). On the kanban branch itself it is inert.
 *
 * No `summarizeField`: it renders a per-column SUM, and there is no number
 * on a task worth totalling. The nearest candidate would be a count, and
 * counts are never ranked or compared here.
 */
 board: {
 label: 'Board',
 type: 'kanban',
 data,
 columns: [{ field: 'subject' }, { field: 'due_date' }, { field: 'owner' }, { field: 'source' }],
 kanban: {
 groupByField: 'status',
 // The card face, in reading order: what it is, when it is owed, whose
 // it is, and where it came from.
 columns: ['subject', 'due_date', 'owner', 'source'],
 },
 inlineEdit: true,
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Gantt. The bar runs `visible_from` → `due_date`, and that span IS the
 * lead time: a bar that starts on its own due date is a task that first
 * appeared the day it was already owed, which is a report on a failure
 * rather than a reminder. `lead_days` on the duty is what produces the
 * length, and this is the only screen where you can see it.
 *
 * Grouped by owner so an overloaded fortnight is visible as one person's
 * row going solid, before the period arrives.
 *
 * The filter is not a scope narrowing, it is a correctness one: the
 * renderer maps a missing date to `new Date()`, so an undated one-off
 * would draw a zero-width bar on TODAY and read as load that does not
 * exist. Both columns are stored and indexed; the unary operators carry
 * their direction in the name and take no value.
 *
 * No `colorField`, deliberately, and this is measured rather than an
 * oversight: the gantt renderer passes `record[colorField]` straight into
 * `backgroundColor`, so `colorField: 'status'` sets `background: "open"` —
 * not a colour, silently dropped, every bar identical. With the key
 * ABSENT the same renderer falls through to its status-derived palette and
 * the bars separate by state. Filed upstream; see the PR body.
 */
 schedule: {
 label: 'Schedule',
 type: 'gantt',
 data,
 columns: [
 { field: 'subject' },
 { field: 'status' },
 { field: 'owner' },
 { field: 'visible_from' },
 { field: 'due_date' },
 ],
 gantt: {
 startDateField: 'visible_from',
 endDateField: 'due_date',
 titleField: 'subject',
 groupByField: 'owner',
 viewMode: 'week',
 tooltipFields: [{ field: 'status' }, { field: 'period_key' }, { field: 'source' }],
 },
 filter: [
 { field: 'visible_from', operator: 'is_not_null' },
 { field: 'due_date', operator: 'is_not_null' },
 ],
 sort: [{ field: 'visible_from', order: 'asc' }],
 },

 /**
 * Timeline — the visual companion to `stalled`. Ordered by
 * `last_update_at`, which `task.hook.ts` stamps on a status change or a
 * note edit and deliberately does NOT advance on an administrative write,
 * so this really is "what has been happening" and not "what has been
 * touched".
 *
 * `colorField` earns its place here: the timeline renderer resolves it
 * against the object's own `status` options and uses the AUTHORED colours
 * (`#35674D` for done, and so on), so this lens and the status badge in
 * every grid read the same.
 */
 recent: {
 label: 'Recent activity',
 type: 'timeline',
 data,
 columns: [{ field: 'subject' }, { field: 'status' }, { field: 'owner' }, { field: 'last_update_at' }],
 timeline: {
 startDateField: 'last_update_at',
 titleField: 'subject',
 colorField: 'status',
 scale: 'day',
 },
 sort: [{ field: 'last_update_at', order: 'desc' }],
 },

 /**
 * The same rows a manager already reads, bucketed by team. `business_unit`
 * is denormalised onto the task at dispatch precisely so a rollup like
 * this survives a later transfer.
 *
 * Groups sort by LABEL — measured in the grid's grouping hook, which sorts
 * group keys with a locale compare on the label and never on the bucket
 * size. Nothing here ranks a unit, or a person, by a count.
 */
 by_unit: {
 label: 'By business unit',
 type: 'grid',
 data,
 columns,
 grouping: { fields: [{ field: 'business_unit' }] },
 bulkActionDefs: bulkActions,
 sort: [{ field: 'due_date', order: 'asc' }],
 },
 },
});
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Kanban, gantt and timeline lenses over the same task data#49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026
 Merged


Kanban, gantt and timeline lenses over the same task data
#49
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
7099555

Add board, schedule, recent, by_unit and catalog_tree lenses


os-warren Sep 1, 2026
997782a

Add test/views.test.ts — binding, field-reference and nav-reachabilit…


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


10 changes: 10 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -28,6 +28,12 @@ export const DulyApp = App.create({
 { id: 'nav_my_duties', type: 'object', objectName: 'duly_duty', viewName: 'mine', label: 'My duties', icon: 'clipboard-list' },
 { id: 'nav_standing', type: 'object', objectName: 'duly_duty', viewName: 'standing', label: 'Standing duties', icon: 'anchor' },
 { id: 'nav_log', type: 'object', objectName: 'duly_log_entry', label: 'Work log', icon: 'notebook-pen' },
 // The board lives HERE, not under Team, and that placement is a
 // product rule rather than taste: dragging a card writes `status`, and
 // managers do not enter status — assigning is their only write. A
 // drag-to-done surface in the manager's section would invite exactly
 // the write the model refuses them.
 { id: 'nav_board', type: 'object', objectName: 'duly_task', viewName: 'board', label: 'Board', icon: 'kanban' },
 ],
 },
 {
Expand All@@ -39,6 +45,9 @@ export const DulyApp = App.create({
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
 { id: 'nav_schedule', type: 'object', objectName: 'duly_task', viewName: 'schedule', label: 'Schedule', icon: 'gantt-chart' },
 { id: 'nav_recent', type: 'object', objectName: 'duly_task', viewName: 'recent', label: 'Recent activity', icon: 'history' },
 { id: 'nav_by_unit', type: 'object', objectName: 'duly_task', viewName: 'by_unit', label: 'By business unit', icon: 'building-2' },
 ],
 },
 {
Expand All@@ -49,6 +58,7 @@ export const DulyApp = App.create({
 children: [
 { id: 'nav_catalog', type: 'object', objectName: 'duly_catalog_item', label: 'Role catalog', icon: 'list-checks' },
 { id: 'nav_all_duties', type: 'object', objectName: 'duly_duty', label: 'All duties', icon: 'library' },
 { id: 'nav_catalog_tree', type: 'object', objectName: 'duly_duty', viewName: 'catalog_tree', label: 'What each team owes', icon: 'folder-tree' },
 ],
 },
 ],
Expand Down

42 changes: 42 additions & 0 deletions
src/views/duty.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -43,5 +43,47 @@ export const DutyViews = defineView({
 columns: [{ field: 'name' }, { field: 'owner' }, { field: 'business_unit' }, { field: 'status' }],
 filter: [{ field: 'form', operator: 'equals', value: 'standing' }],
 },

 /**
 * "What does this team owe" — every duty bucketed by business unit, then
 * by the one accountable person inside it, both levels collapsible.
 *
 * ⚠️ DELIBERATELY `type: 'grid'` + `grouping`, NOT `type: 'tree'`, and the
 * difference is not cosmetic. The platform's `tree` view is a
 * SELF-REFERENCING hierarchy: `TreeConfigSchema` takes a `parentField`
 * single-parent pointer, and the renderer nests a record under another
 * record of the SAME object by matching `record[parentField]` against the
 * sibling ids. `duly_duty` has no self-reference — its lookups point at
 * `sys_business_unit`, `duly_catalog_item` and a user — so a `type: 'tree'`
 * view here resolves no parent for any row, puts every duty at depth 0 and
 * renders a FLAT list. The renderer never reads `grouping`, so declaring
 * the two levels alongside it would change nothing, and nothing in
 * `pnpm validate` says so: the `view/layout-without-binding` gate does not
 * cover `tree` at all. That is the exact "renders wrong while authoring
 * reports success" shape this app's views exist to avoid, so it is not
 * shipped and the gap is filed upstream instead (see the PR body).
 *
 * The grid's grouping hook is the honest expression of the same idea and
 * it is measured, not assumed: it recurses through `grouping.fields`,
 * building nested `subgroups` with per-level collapse — a real two-level
 * hierarchy. Group keys sort by LABEL, never by bucket size, so no team
 * and no person is ever ordered by how much they owe.
 */
 catalog_tree: {
 label: 'What each team owes',
 type: 'grid',
 data,
 columns: [
 { field: 'name' },
 { field: 'form' },
 { field: 'frequency' },
 { field: 'source' },
 { field: 'status' },
 ],
 grouping: {
 fields: [{ field: 'business_unit' }, { field: 'owner' }],
 },
 sort: [{ field: 'name', order: 'asc' }],
 },
 },
});

131 changes: 131 additions & 0 deletions
src/views/task.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -161,5 +161,136 @@ export const TaskViews = defineView({
 },
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Kanban. Columns come from `duly_task.status` — the renderer reads the
 * field's own `options` for the column set, their order and their labels
 * (measured in the console's `plugin-kanban`), so the board cannot drift
 * from the object.
 *
 * Dragging a card writes ONE field. Measured against the renderer's move
 * handler: `dataSource.update(object, id, { [groupBy]: toColumnId })` —
 * `status` and nothing else, which is the same write the row action does.
 * It is NOT gated on `inlineEdit`; it is gated on update permission, so a
 * user who may not write `status` gets the platform's rejection rather
 * than a silent no-op.
 *
 * `inlineEdit` is still declared, and it is not decoration: the toolbar
 * lets a viewer switch this view to its grid visualisation, and the
 * adapter honours `inlineEdit` on that branch (`editable:` is set in the
 * grid case only). On the kanban branch itself it is inert.
 *
 * No `summarizeField`: it renders a per-column SUM, and there is no number
 * on a task worth totalling. The nearest candidate would be a count, and
 * counts are never ranked or compared here.
 */
 board: {
 label: 'Board',
 type: 'kanban',
 data,
 columns: [{ field: 'subject' }, { field: 'due_date' }, { field: 'owner' }, { field: 'source' }],
 kanban: {
 groupByField: 'status',
 // The card face, in reading order: what it is, when it is owed, whose
 // it is, and where it came from.
 columns: ['subject', 'due_date', 'owner', 'source'],
 },
 inlineEdit: true,
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Gantt. The bar runs `visible_from` → `due_date`, and that span IS the
 * lead time: a bar that starts on its own due date is a task that first
 * appeared the day it was already owed, which is a report on a failure
 * rather than a reminder. `lead_days` on the duty is what produces the
 * length, and this is the only screen where you can see it.
 *
 * Grouped by owner so an overloaded fortnight is visible as one person's
 * row going solid, before the period arrives.
 *
 * The filter is not a scope narrowing, it is a correctness one: the
 * renderer maps a missing date to `new Date()`, so an undated one-off
 * would draw a zero-width bar on TODAY and read as load that does not
 * exist. Both columns are stored and indexed; the unary operators carry
 * their direction in the name and take no value.
 *
 * No `colorField`, deliberately, and this is measured rather than an
 * oversight: the gantt renderer passes `record[colorField]` straight into
 * `backgroundColor`, so `colorField: 'status'` sets `background: "open"` —
 * not a colour, silently dropped, every bar identical. With the key
 * ABSENT the same renderer falls through to its status-derived palette and
 * the bars separate by state. Filed upstream; see the PR body.
 */
 schedule: {
 label: 'Schedule',
 type: 'gantt',
 data,
 columns: [
 { field: 'subject' },
 { field: 'status' },
 { field: 'owner' },
 { field: 'visible_from' },
 { field: 'due_date' },
 ],
 gantt: {
 startDateField: 'visible_from',
 endDateField: 'due_date',
 titleField: 'subject',
 groupByField: 'owner',
 viewMode: 'week',
 tooltipFields: [{ field: 'status' }, { field: 'period_key' }, { field: 'source' }],
 },
 filter: [
 { field: 'visible_from', operator: 'is_not_null' },
 { field: 'due_date', operator: 'is_not_null' },
 ],
 sort: [{ field: 'visible_from', order: 'asc' }],
 },

 /**
 * Timeline — the visual companion to `stalled`. Ordered by
 * `last_update_at`, which `task.hook.ts` stamps on a status change or a
 * note edit and deliberately does NOT advance on an administrative write,
 * so this really is "what has been happening" and not "what has been
 * touched".
 *
 * `colorField` earns its place here: the timeline renderer resolves it
 * against the object's own `status` options and uses the AUTHORED colours
 * (`#35674D` for done, and so on), so this lens and the status badge in
 * every grid read the same.
 */
 recent: {
 label: 'Recent activity',
 type: 'timeline',
 data,
 columns: [{ field: 'subject' }, { field: 'status' }, { field: 'owner' }, { field: 'last_update_at' }],
 timeline: {
 startDateField: 'last_update_at',
 titleField: 'subject',
 colorField: 'status',
 scale: 'day',
 },
 sort: [{ field: 'last_update_at', order: 'desc' }],
 },

 /**
 * The same rows a manager already reads, bucketed by team. `business_unit`
 * is denormalised onto the task at dispatch precisely so a rollup like
 * this survives a later transfer.
 *
 * Groups sort by LABEL — measured in the grid's grouping hook, which sorts
 * group keys with a locale compare on the label and never on the bucket
 * size. Nothing here ranks a unit, or a person, by a count.
 */
 by_unit: {
 label: 'By business unit',
 type: 'grid',
 data,
 columns,
 grouping: { fields: [{ field: 'business_unit' }] },
 bulkActionDefs: bulkActions,
 sort: [{ field: 'due_date', order: 'asc' }],
 },
 },
});
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
Kanban, gantt and timeline lenses over the same task data#49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026
 Merged


Kanban, gantt and timeline lenses over the same task data
#49
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
7099555

Add board, schedule, recent, by_unit and catalog_tree lenses


os-warren Sep 1, 2026
997782a

Add test/views.test.ts — binding, field-reference and nav-reachabilit…


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


10 changes: 10 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -28,6 +28,12 @@ export const DulyApp = App.create({
 { id: 'nav_my_duties', type: 'object', objectName: 'duly_duty', viewName: 'mine', label: 'My duties', icon: 'clipboard-list' },
 { id: 'nav_standing', type: 'object', objectName: 'duly_duty', viewName: 'standing', label: 'Standing duties', icon: 'anchor' },
 { id: 'nav_log', type: 'object', objectName: 'duly_log_entry', label: 'Work log', icon: 'notebook-pen' },
 // The board lives HERE, not under Team, and that placement is a
 // product rule rather than taste: dragging a card writes `status`, and
 // managers do not enter status — assigning is their only write. A
 // drag-to-done surface in the manager's section would invite exactly
 // the write the model refuses them.
 { id: 'nav_board', type: 'object', objectName: 'duly_task', viewName: 'board', label: 'Board', icon: 'kanban' },
 ],
 },
 {
Expand All@@ -39,6 +45,9 @@ export const DulyApp = App.create({
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
 { id: 'nav_schedule', type: 'object', objectName: 'duly_task', viewName: 'schedule', label: 'Schedule', icon: 'gantt-chart' },
 { id: 'nav_recent', type: 'object', objectName: 'duly_task', viewName: 'recent', label: 'Recent activity', icon: 'history' },
 { id: 'nav_by_unit', type: 'object', objectName: 'duly_task', viewName: 'by_unit', label: 'By business unit', icon: 'building-2' },
 ],
 },
 {
Expand All@@ -49,6 +58,7 @@ export const DulyApp = App.create({
 children: [
 { id: 'nav_catalog', type: 'object', objectName: 'duly_catalog_item', label: 'Role catalog', icon: 'list-checks' },
 { id: 'nav_all_duties', type: 'object', objectName: 'duly_duty', label: 'All duties', icon: 'library' },
 { id: 'nav_catalog_tree', type: 'object', objectName: 'duly_duty', viewName: 'catalog_tree', label: 'What each team owes', icon: 'folder-tree' },
 ],
 },
 ],
Expand Down

42 changes: 42 additions & 0 deletions
src/views/duty.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -43,5 +43,47 @@ export const DutyViews = defineView({
 columns: [{ field: 'name' }, { field: 'owner' }, { field: 'business_unit' }, { field: 'status' }],
 filter: [{ field: 'form', operator: 'equals', value: 'standing' }],
 },

 /**
 * "What does this team owe" — every duty bucketed by business unit, then
 * by the one accountable person inside it, both levels collapsible.
 *
 * ⚠️ DELIBERATELY `type: 'grid'` + `grouping`, NOT `type: 'tree'`, and the
 * difference is not cosmetic. The platform's `tree` view is a
 * SELF-REFERENCING hierarchy: `TreeConfigSchema` takes a `parentField`
 * single-parent pointer, and the renderer nests a record under another
 * record of the SAME object by matching `record[parentField]` against the
 * sibling ids. `duly_duty` has no self-reference — its lookups point at
 * `sys_business_unit`, `duly_catalog_item` and a user — so a `type: 'tree'`
 * view here resolves no parent for any row, puts every duty at depth 0 and
 * renders a FLAT list. The renderer never reads `grouping`, so declaring
 * the two levels alongside it would change nothing, and nothing in
 * `pnpm validate` says so: the `view/layout-without-binding` gate does not
 * cover `tree` at all. That is the exact "renders wrong while authoring
 * reports success" shape this app's views exist to avoid, so it is not
 * shipped and the gap is filed upstream instead (see the PR body).
 *
 * The grid's grouping hook is the honest expression of the same idea and
 * it is measured, not assumed: it recurses through `grouping.fields`,
 * building nested `subgroups` with per-level collapse — a real two-level
 * hierarchy. Group keys sort by LABEL, never by bucket size, so no team
 * and no person is ever ordered by how much they owe.
 */
 catalog_tree: {
 label: 'What each team owes',
 type: 'grid',
 data,
 columns: [
 { field: 'name' },
 { field: 'form' },
 { field: 'frequency' },
 { field: 'source' },
 { field: 'status' },
 ],
 grouping: {
 fields: [{ field: 'business_unit' }, { field: 'owner' }],
 },
 sort: [{ field: 'name', order: 'asc' }],
 },
 },
});

131 changes: 131 additions & 0 deletions
src/views/task.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -161,5 +161,136 @@ export const TaskViews = defineView({
 },
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Kanban. Columns come from `duly_task.status` — the renderer reads the
 * field's own `options` for the column set, their order and their labels
 * (measured in the console's `plugin-kanban`), so the board cannot drift
 * from the object.
 *
 * Dragging a card writes ONE field. Measured against the renderer's move
 * handler: `dataSource.update(object, id, { [groupBy]: toColumnId })` —
 * `status` and nothing else, which is the same write the row action does.
 * It is NOT gated on `inlineEdit`; it is gated on update permission, so a
 * user who may not write `status` gets the platform's rejection rather
 * than a silent no-op.
 *
 * `inlineEdit` is still declared, and it is not decoration: the toolbar
 * lets a viewer switch this view to its grid visualisation, and the
 * adapter honours `inlineEdit` on that branch (`editable:` is set in the
 * grid case only). On the kanban branch itself it is inert.
 *
 * No `summarizeField`: it renders a per-column SUM, and there is no number
 * on a task worth totalling. The nearest candidate would be a count, and
 * counts are never ranked or compared here.
 */
 board: {
 label: 'Board',
 type: 'kanban',
 data,
 columns: [{ field: 'subject' }, { field: 'due_date' }, { field: 'owner' }, { field: 'source' }],
 kanban: {
 groupByField: 'status',
 // The card face, in reading order: what it is, when it is owed, whose
 // it is, and where it came from.
 columns: ['subject', 'due_date', 'owner', 'source'],
 },
 inlineEdit: true,
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Gantt. The bar runs `visible_from` → `due_date`, and that span IS the
 * lead time: a bar that starts on its own due date is a task that first
 * appeared the day it was already owed, which is a report on a failure
 * rather than a reminder. `lead_days` on the duty is what produces the
 * length, and this is the only screen where you can see it.
 *
 * Grouped by owner so an overloaded fortnight is visible as one person's
 * row going solid, before the period arrives.
 *
 * The filter is not a scope narrowing, it is a correctness one: the
 * renderer maps a missing date to `new Date()`, so an undated one-off
 * would draw a zero-width bar on TODAY and read as load that does not
 * exist. Both columns are stored and indexed; the unary operators carry
 * their direction in the name and take no value.
 *
 * No `colorField`, deliberately, and this is measured rather than an
 * oversight: the gantt renderer passes `record[colorField]` straight into
 * `backgroundColor`, so `colorField: 'status'` sets `background: "open"` —
 * not a colour, silently dropped, every bar identical. With the key
 * ABSENT the same renderer falls through to its status-derived palette and
 * the bars separate by state. Filed upstream; see the PR body.
 */
 schedule: {
 label: 'Schedule',
 type: 'gantt',
 data,
 columns: [
 { field: 'subject' },
 { field: 'status' },
 { field: 'owner' },
 { field: 'visible_from' },
 { field: 'due_date' },
 ],
 gantt: {
 startDateField: 'visible_from',
 endDateField: 'due_date',
 titleField: 'subject',
 groupByField: 'owner',
 viewMode: 'week',
 tooltipFields: [{ field: 'status' }, { field: 'period_key' }, { field: 'source' }],
 },
 filter: [
 { field: 'visible_from', operator: 'is_not_null' },
 { field: 'due_date', operator: 'is_not_null' },
 ],
 sort: [{ field: 'visible_from', order: 'asc' }],
 },

 /**
 * Timeline — the visual companion to `stalled`. Ordered by
 * `last_update_at`, which `task.hook.ts` stamps on a status change or a
 * note edit and deliberately does NOT advance on an administrative write,
 * so this really is "what has been happening" and not "what has been
 * touched".
 *
 * `colorField` earns its place here: the timeline renderer resolves it
 * against the object's own `status` options and uses the AUTHORED colours
 * (`#35674D` for done, and so on), so this lens and the status badge in
 * every grid read the same.
 */
 recent: {
 label: 'Recent activity',
 type: 'timeline',
 data,
 columns: [{ field: 'subject' }, { field: 'status' }, { field: 'owner' }, { field: 'last_update_at' }],
 timeline: {
 startDateField: 'last_update_at',
 titleField: 'subject',
 colorField: 'status',
 scale: 'day',
 },
 sort: [{ field: 'last_update_at', order: 'desc' }],
 },

 /**
 * The same rows a manager already reads, bucketed by team. `business_unit`
 * is denormalised onto the task at dispatch precisely so a rollup like
 * this survives a later transfer.
 *
 * Groups sort by LABEL — measured in the grid's grouping hook, which sorts
 * group keys with a locale compare on the label and never on the bucket
 * size. Nothing here ranks a unit, or a person, by a count.
 */
 by_unit: {
 label: 'By business unit',
 type: 'grid',
 data,
 columns,
 grouping: { fields: [{ field: 'business_unit' }] },
 bulkActionDefs: bulkActions,
 sort: [{ field: 'due_date', order: 'asc' }],
 },
 },
});
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Kanban, gantt and timeline lenses over the same task data#49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026
 Merged


Kanban, gantt and timeline lenses over the same task data
#49
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
7099555

Add board, schedule, recent, by_unit and catalog_tree lenses


os-warren Sep 1, 2026
997782a

Add test/views.test.ts — binding, field-reference and nav-reachabilit…


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


10 changes: 10 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -28,6 +28,12 @@ export const DulyApp = App.create({
 { id: 'nav_my_duties', type: 'object', objectName: 'duly_duty', viewName: 'mine', label: 'My duties', icon: 'clipboard-list' },
 { id: 'nav_standing', type: 'object', objectName: 'duly_duty', viewName: 'standing', label: 'Standing duties', icon: 'anchor' },
 { id: 'nav_log', type: 'object', objectName: 'duly_log_entry', label: 'Work log', icon: 'notebook-pen' },
 // The board lives HERE, not under Team, and that placement is a
 // product rule rather than taste: dragging a card writes `status`, and
 // managers do not enter status — assigning is their only write. A
 // drag-to-done surface in the manager's section would invite exactly
 // the write the model refuses them.
 { id: 'nav_board', type: 'object', objectName: 'duly_task', viewName: 'board', label: 'Board', icon: 'kanban' },
 ],
 },
 {
Expand All@@ -39,6 +45,9 @@ export const DulyApp = App.create({
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
 { id: 'nav_schedule', type: 'object', objectName: 'duly_task', viewName: 'schedule', label: 'Schedule', icon: 'gantt-chart' },
 { id: 'nav_recent', type: 'object', objectName: 'duly_task', viewName: 'recent', label: 'Recent activity', icon: 'history' },
 { id: 'nav_by_unit', type: 'object', objectName: 'duly_task', viewName: 'by_unit', label: 'By business unit', icon: 'building-2' },
 ],
 },
 {
Expand All@@ -49,6 +58,7 @@ export const DulyApp = App.create({
 children: [
 { id: 'nav_catalog', type: 'object', objectName: 'duly_catalog_item', label: 'Role catalog', icon: 'list-checks' },
 { id: 'nav_all_duties', type: 'object', objectName: 'duly_duty', label: 'All duties', icon: 'library' },
 { id: 'nav_catalog_tree', type: 'object', objectName: 'duly_duty', viewName: 'catalog_tree', label: 'What each team owes', icon: 'folder-tree' },
 ],
 },
 ],
Expand Down

42 changes: 42 additions & 0 deletions
src/views/duty.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -43,5 +43,47 @@ export const DutyViews = defineView({
 columns: [{ field: 'name' }, { field: 'owner' }, { field: 'business_unit' }, { field: 'status' }],
 filter: [{ field: 'form', operator: 'equals', value: 'standing' }],
 },

 /**
 * "What does this team owe" — every duty bucketed by business unit, then
 * by the one accountable person inside it, both levels collapsible.
 *
 * ⚠️ DELIBERATELY `type: 'grid'` + `grouping`, NOT `type: 'tree'`, and the
 * difference is not cosmetic. The platform's `tree` view is a
 * SELF-REFERENCING hierarchy: `TreeConfigSchema` takes a `parentField`
 * single-parent pointer, and the renderer nests a record under another
 * record of the SAME object by matching `record[parentField]` against the
 * sibling ids. `duly_duty` has no self-reference — its lookups point at
 * `sys_business_unit`, `duly_catalog_item` and a user — so a `type: 'tree'`
 * view here resolves no parent for any row, puts every duty at depth 0 and
 * renders a FLAT list. The renderer never reads `grouping`, so declaring
 * the two levels alongside it would change nothing, and nothing in
 * `pnpm validate` says so: the `view/layout-without-binding` gate does not
 * cover `tree` at all. That is the exact "renders wrong while authoring
 * reports success" shape this app's views exist to avoid, so it is not
 * shipped and the gap is filed upstream instead (see the PR body).
 *
 * The grid's grouping hook is the honest expression of the same idea and
 * it is measured, not assumed: it recurses through `grouping.fields`,
 * building nested `subgroups` with per-level collapse — a real two-level
 * hierarchy. Group keys sort by LABEL, never by bucket size, so no team
 * and no person is ever ordered by how much they owe.
 */
 catalog_tree: {
 label: 'What each team owes',
 type: 'grid',
 data,
 columns: [
 { field: 'name' },
 { field: 'form' },
 { field: 'frequency' },
 { field: 'source' },
 { field: 'status' },
 ],
 grouping: {
 fields: [{ field: 'business_unit' }, { field: 'owner' }],
 },
 sort: [{ field: 'name', order: 'asc' }],
 },
 },
});

131 changes: 131 additions & 0 deletions
src/views/task.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -161,5 +161,136 @@ export const TaskViews = defineView({
 },
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Kanban. Columns come from `duly_task.status` — the renderer reads the
 * field's own `options` for the column set, their order and their labels
 * (measured in the console's `plugin-kanban`), so the board cannot drift
 * from the object.
 *
 * Dragging a card writes ONE field. Measured against the renderer's move
 * handler: `dataSource.update(object, id, { [groupBy]: toColumnId })` —
 * `status` and nothing else, which is the same write the row action does.
 * It is NOT gated on `inlineEdit`; it is gated on update permission, so a
 * user who may not write `status` gets the platform's rejection rather
 * than a silent no-op.
 *
 * `inlineEdit` is still declared, and it is not decoration: the toolbar
 * lets a viewer switch this view to its grid visualisation, and the
 * adapter honours `inlineEdit` on that branch (`editable:` is set in the
 * grid case only). On the kanban branch itself it is inert.
 *
 * No `summarizeField`: it renders a per-column SUM, and there is no number
 * on a task worth totalling. The nearest candidate would be a count, and
 * counts are never ranked or compared here.
 */
 board: {
 label: 'Board',
 type: 'kanban',
 data,
 columns: [{ field: 'subject' }, { field: 'due_date' }, { field: 'owner' }, { field: 'source' }],
 kanban: {
 groupByField: 'status',
 // The card face, in reading order: what it is, when it is owed, whose
 // it is, and where it came from.
 columns: ['subject', 'due_date', 'owner', 'source'],
 },
 inlineEdit: true,
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Gantt. The bar runs `visible_from` → `due_date`, and that span IS the
 * lead time: a bar that starts on its own due date is a task that first
 * appeared the day it was already owed, which is a report on a failure
 * rather than a reminder. `lead_days` on the duty is what produces the
 * length, and this is the only screen where you can see it.
 *
 * Grouped by owner so an overloaded fortnight is visible as one person's
 * row going solid, before the period arrives.
 *
 * The filter is not a scope narrowing, it is a correctness one: the
 * renderer maps a missing date to `new Date()`, so an undated one-off
 * would draw a zero-width bar on TODAY and read as load that does not
 * exist. Both columns are stored and indexed; the unary operators carry
 * their direction in the name and take no value.
 *
 * No `colorField`, deliberately, and this is measured rather than an
 * oversight: the gantt renderer passes `record[colorField]` straight into
 * `backgroundColor`, so `colorField: 'status'` sets `background: "open"` —
 * not a colour, silently dropped, every bar identical. With the key
 * ABSENT the same renderer falls through to its status-derived palette and
 * the bars separate by state. Filed upstream; see the PR body.
 */
 schedule: {
 label: 'Schedule',
 type: 'gantt',
 data,
 columns: [
 { field: 'subject' },
 { field: 'status' },
 { field: 'owner' },
 { field: 'visible_from' },
 { field: 'due_date' },
 ],
 gantt: {
 startDateField: 'visible_from',
 endDateField: 'due_date',
 titleField: 'subject',
 groupByField: 'owner',
 viewMode: 'week',
 tooltipFields: [{ field: 'status' }, { field: 'period_key' }, { field: 'source' }],
 },
 filter: [
 { field: 'visible_from', operator: 'is_not_null' },
 { field: 'due_date', operator: 'is_not_null' },
 ],
 sort: [{ field: 'visible_from', order: 'asc' }],
 },

 /**
 * Timeline — the visual companion to `stalled`. Ordered by
 * `last_update_at`, which `task.hook.ts` stamps on a status change or a
 * note edit and deliberately does NOT advance on an administrative write,
 * so this really is "what has been happening" and not "what has been
 * touched".
 *
 * `colorField` earns its place here: the timeline renderer resolves it
 * against the object's own `status` options and uses the AUTHORED colours
 * (`#35674D` for done, and so on), so this lens and the status badge in
 * every grid read the same.
 */
 recent: {
 label: 'Recent activity',
 type: 'timeline',
 data,
 columns: [{ field: 'subject' }, { field: 'status' }, { field: 'owner' }, { field: 'last_update_at' }],
 timeline: {
 startDateField: 'last_update_at',
 titleField: 'subject',
 colorField: 'status',
 scale: 'day',
 },
 sort: [{ field: 'last_update_at', order: 'desc' }],
 },

 /**
 * The same rows a manager already reads, bucketed by team. `business_unit`
 * is denormalised onto the task at dispatch precisely so a rollup like
 * this survives a later transfer.
 *
 * Groups sort by LABEL — measured in the grid's grouping hook, which sorts
 * group keys with a locale compare on the label and never on the bucket
 * size. Nothing here ranks a unit, or a person, by a count.
 */
 by_unit: {
 label: 'By business unit',
 type: 'grid',
 data,
 columns,
 grouping: { fields: [{ field: 'business_unit' }] },
 bulkActionDefs: bulkActions,
 sort: [{ field: 'due_date', order: 'asc' }],
 },
 },
});
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
Kanban, gantt and timeline lenses over the same task data#49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026
 Merged


Kanban, gantt and timeline lenses over the same task data
#49
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
7099555

Add board, schedule, recent, by_unit and catalog_tree lenses


os-warren Sep 1, 2026
997782a

Add test/views.test.ts — binding, field-reference and nav-reachabilit…


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


10 changes: 10 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -28,6 +28,12 @@ export const DulyApp = App.create({
 { id: 'nav_my_duties', type: 'object', objectName: 'duly_duty', viewName: 'mine', label: 'My duties', icon: 'clipboard-list' },
 { id: 'nav_standing', type: 'object', objectName: 'duly_duty', viewName: 'standing', label: 'Standing duties', icon: 'anchor' },
 { id: 'nav_log', type: 'object', objectName: 'duly_log_entry', label: 'Work log', icon: 'notebook-pen' },
 // The board lives HERE, not under Team, and that placement is a
 // product rule rather than taste: dragging a card writes `status`, and
 // managers do not enter status — assigning is their only write. A
 // drag-to-done surface in the manager's section would invite exactly
 // the write the model refuses them.
 { id: 'nav_board', type: 'object', objectName: 'duly_task', viewName: 'board', label: 'Board', icon: 'kanban' },
 ],
 },
 {
Expand All@@ -39,6 +45,9 @@ export const DulyApp = App.create({
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
 { id: 'nav_schedule', type: 'object', objectName: 'duly_task', viewName: 'schedule', label: 'Schedule', icon: 'gantt-chart' },
 { id: 'nav_recent', type: 'object', objectName: 'duly_task', viewName: 'recent', label: 'Recent activity', icon: 'history' },
 { id: 'nav_by_unit', type: 'object', objectName: 'duly_task', viewName: 'by_unit', label: 'By business unit', icon: 'building-2' },
 ],
 },
 {
Expand All@@ -49,6 +58,7 @@ export const DulyApp = App.create({
 children: [
 { id: 'nav_catalog', type: 'object', objectName: 'duly_catalog_item', label: 'Role catalog', icon: 'list-checks' },
 { id: 'nav_all_duties', type: 'object', objectName: 'duly_duty', label: 'All duties', icon: 'library' },
 { id: 'nav_catalog_tree', type: 'object', objectName: 'duly_duty', viewName: 'catalog_tree', label: 'What each team owes', icon: 'folder-tree' },
 ],
 },
 ],
Expand Down

42 changes: 42 additions & 0 deletions
src/views/duty.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -43,5 +43,47 @@ export const DutyViews = defineView({
 columns: [{ field: 'name' }, { field: 'owner' }, { field: 'business_unit' }, { field: 'status' }],
 filter: [{ field: 'form', operator: 'equals', value: 'standing' }],
 },

 /**
 * "What does this team owe" — every duty bucketed by business unit, then
 * by the one accountable person inside it, both levels collapsible.
 *
 * ⚠️ DELIBERATELY `type: 'grid'` + `grouping`, NOT `type: 'tree'`, and the
 * difference is not cosmetic. The platform's `tree` view is a
 * SELF-REFERENCING hierarchy: `TreeConfigSchema` takes a `parentField`
 * single-parent pointer, and the renderer nests a record under another
 * record of the SAME object by matching `record[parentField]` against the
 * sibling ids. `duly_duty` has no self-reference — its lookups point at
 * `sys_business_unit`, `duly_catalog_item` and a user — so a `type: 'tree'`
 * view here resolves no parent for any row, puts every duty at depth 0 and
 * renders a FLAT list. The renderer never reads `grouping`, so declaring
 * the two levels alongside it would change nothing, and nothing in
 * `pnpm validate` says so: the `view/layout-without-binding` gate does not
 * cover `tree` at all. That is the exact "renders wrong while authoring
 * reports success" shape this app's views exist to avoid, so it is not
 * shipped and the gap is filed upstream instead (see the PR body).
 *
 * The grid's grouping hook is the honest expression of the same idea and
 * it is measured, not assumed: it recurses through `grouping.fields`,
 * building nested `subgroups` with per-level collapse — a real two-level
 * hierarchy. Group keys sort by LABEL, never by bucket size, so no team
 * and no person is ever ordered by how much they owe.
 */
 catalog_tree: {
 label: 'What each team owes',
 type: 'grid',
 data,
 columns: [
 { field: 'name' },
 { field: 'form' },
 { field: 'frequency' },
 { field: 'source' },
 { field: 'status' },
 ],
 grouping: {
 fields: [{ field: 'business_unit' }, { field: 'owner' }],
 },
 sort: [{ field: 'name', order: 'asc' }],
 },
 },
});

131 changes: 131 additions & 0 deletions
src/views/task.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -161,5 +161,136 @@ export const TaskViews = defineView({
 },
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Kanban. Columns come from `duly_task.status` — the renderer reads the
 * field's own `options` for the column set, their order and their labels
 * (measured in the console's `plugin-kanban`), so the board cannot drift
 * from the object.
 *
 * Dragging a card writes ONE field. Measured against the renderer's move
 * handler: `dataSource.update(object, id, { [groupBy]: toColumnId })` —
 * `status` and nothing else, which is the same write the row action does.
 * It is NOT gated on `inlineEdit`; it is gated on update permission, so a
 * user who may not write `status` gets the platform's rejection rather
 * than a silent no-op.
 *
 * `inlineEdit` is still declared, and it is not decoration: the toolbar
 * lets a viewer switch this view to its grid visualisation, and the
 * adapter honours `inlineEdit` on that branch (`editable:` is set in the
 * grid case only). On the kanban branch itself it is inert.
 *
 * No `summarizeField`: it renders a per-column SUM, and there is no number
 * on a task worth totalling. The nearest candidate would be a count, and
 * counts are never ranked or compared here.
 */
 board: {
 label: 'Board',
 type: 'kanban',
 data,
 columns: [{ field: 'subject' }, { field: 'due_date' }, { field: 'owner' }, { field: 'source' }],
 kanban: {
 groupByField: 'status',
 // The card face, in reading order: what it is, when it is owed, whose
 // it is, and where it came from.
 columns: ['subject', 'due_date', 'owner', 'source'],
 },
 inlineEdit: true,
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Gantt. The bar runs `visible_from` → `due_date`, and that span IS the
 * lead time: a bar that starts on its own due date is a task that first
 * appeared the day it was already owed, which is a report on a failure
 * rather than a reminder. `lead_days` on the duty is what produces the
 * length, and this is the only screen where you can see it.
 *
 * Grouped by owner so an overloaded fortnight is visible as one person's
 * row going solid, before the period arrives.
 *
 * The filter is not a scope narrowing, it is a correctness one: the
 * renderer maps a missing date to `new Date()`, so an undated one-off
 * would draw a zero-width bar on TODAY and read as load that does not
 * exist. Both columns are stored and indexed; the unary operators carry
 * their direction in the name and take no value.
 *
 * No `colorField`, deliberately, and this is measured rather than an
 * oversight: the gantt renderer passes `record[colorField]` straight into
 * `backgroundColor`, so `colorField: 'status'` sets `background: "open"` —
 * not a colour, silently dropped, every bar identical. With the key
 * ABSENT the same renderer falls through to its status-derived palette and
 * the bars separate by state. Filed upstream; see the PR body.
 */
 schedule: {
 label: 'Schedule',
 type: 'gantt',
 data,
 columns: [
 { field: 'subject' },
 { field: 'status' },
 { field: 'owner' },
 { field: 'visible_from' },
 { field: 'due_date' },
 ],
 gantt: {
 startDateField: 'visible_from',
 endDateField: 'due_date',
 titleField: 'subject',
 groupByField: 'owner',
 viewMode: 'week',
 tooltipFields: [{ field: 'status' }, { field: 'period_key' }, { field: 'source' }],
 },
 filter: [
 { field: 'visible_from', operator: 'is_not_null' },
 { field: 'due_date', operator: 'is_not_null' },
 ],
 sort: [{ field: 'visible_from', order: 'asc' }],
 },

 /**
 * Timeline — the visual companion to `stalled`. Ordered by
 * `last_update_at`, which `task.hook.ts` stamps on a status change or a
 * note edit and deliberately does NOT advance on an administrative write,
 * so this really is "what has been happening" and not "what has been
 * touched".
 *
 * `colorField` earns its place here: the timeline renderer resolves it
 * against the object's own `status` options and uses the AUTHORED colours
 * (`#35674D` for done, and so on), so this lens and the status badge in
 * every grid read the same.
 */
 recent: {
 label: 'Recent activity',
 type: 'timeline',
 data,
 columns: [{ field: 'subject' }, { field: 'status' }, { field: 'owner' }, { field: 'last_update_at' }],
 timeline: {
 startDateField: 'last_update_at',
 titleField: 'subject',
 colorField: 'status',
 scale: 'day',
 },
 sort: [{ field: 'last_update_at', order: 'desc' }],
 },

 /**
 * The same rows a manager already reads, bucketed by team. `business_unit`
 * is denormalised onto the task at dispatch precisely so a rollup like
 * this survives a later transfer.
 *
 * Groups sort by LABEL — measured in the grid's grouping hook, which sorts
 * group keys with a locale compare on the label and never on the bucket
 * size. Nothing here ranks a unit, or a person, by a count.
 */
 by_unit: {
 label: 'By business unit',
 type: 'grid',
 data,
 columns,
 grouping: { fields: [{ field: 'business_unit' }] },
 bulkActionDefs: bulkActions,
 sort: [{ field: 'due_date', order: 'asc' }],
 },
 },
});
Loading
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
Kanban, gantt and timeline lenses over the same task data#49

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-warren
merged 2 commits into

from

Sep 1, 2026
 Merged


Kanban, gantt and timeline lenses over the same task data
#49
Show file tree
Hide file tree
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
7099555

Add board, schedule, recent, by_unit and catalog_tree lenses


os-warren Sep 1, 2026
997782a

Add test/views.test.ts — binding, field-reference and nav-reachabilit…


os-warren Sep 1, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


10 changes: 10 additions & 0 deletions
src/apps/duly.app.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -28,6 +28,12 @@ export const DulyApp = App.create({
 { id: 'nav_my_duties', type: 'object', objectName: 'duly_duty', viewName: 'mine', label: 'My duties', icon: 'clipboard-list' },
 { id: 'nav_standing', type: 'object', objectName: 'duly_duty', viewName: 'standing', label: 'Standing duties', icon: 'anchor' },
 { id: 'nav_log', type: 'object', objectName: 'duly_log_entry', label: 'Work log', icon: 'notebook-pen' },
 // The board lives HERE, not under Team, and that placement is a
 // product rule rather than taste: dragging a card writes `status`, and
 // managers do not enter status — assigning is their only write. A
 // drag-to-done surface in the manager's section would invite exactly
 // the write the model refuses them.
 { id: 'nav_board', type: 'object', objectName: 'duly_task', viewName: 'board', label: 'Board', icon: 'kanban' },
 ],
 },
 {
Expand All@@ -39,6 +45,9 @@ export const DulyApp = App.create({
 { id: 'nav_late', type: 'object', objectName: 'duly_task', viewName: 'late', label: 'Late', icon: 'alert-circle' },
 { id: 'nav_stalled', type: 'object', objectName: 'duly_task', viewName: 'stalled', label: 'Not moving', icon: 'pause-circle' },
 { id: 'nav_assignments', type: 'object', objectName: 'duly_assignment', viewName: 'sent_by_me', label: 'Assignments', icon: 'send' },
 { id: 'nav_schedule', type: 'object', objectName: 'duly_task', viewName: 'schedule', label: 'Schedule', icon: 'gantt-chart' },
 { id: 'nav_recent', type: 'object', objectName: 'duly_task', viewName: 'recent', label: 'Recent activity', icon: 'history' },
 { id: 'nav_by_unit', type: 'object', objectName: 'duly_task', viewName: 'by_unit', label: 'By business unit', icon: 'building-2' },
 ],
 },
 {
Expand All@@ -49,6 +58,7 @@ export const DulyApp = App.create({
 children: [
 { id: 'nav_catalog', type: 'object', objectName: 'duly_catalog_item', label: 'Role catalog', icon: 'list-checks' },
 { id: 'nav_all_duties', type: 'object', objectName: 'duly_duty', label: 'All duties', icon: 'library' },
 { id: 'nav_catalog_tree', type: 'object', objectName: 'duly_duty', viewName: 'catalog_tree', label: 'What each team owes', icon: 'folder-tree' },
 ],
 },
 ],
Expand Down

42 changes: 42 additions & 0 deletions
src/views/duty.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -43,5 +43,47 @@ export const DutyViews = defineView({
 columns: [{ field: 'name' }, { field: 'owner' }, { field: 'business_unit' }, { field: 'status' }],
 filter: [{ field: 'form', operator: 'equals', value: 'standing' }],
 },

 /**
 * "What does this team owe" — every duty bucketed by business unit, then
 * by the one accountable person inside it, both levels collapsible.
 *
 * ⚠️ DELIBERATELY `type: 'grid'` + `grouping`, NOT `type: 'tree'`, and the
 * difference is not cosmetic. The platform's `tree` view is a
 * SELF-REFERENCING hierarchy: `TreeConfigSchema` takes a `parentField`
 * single-parent pointer, and the renderer nests a record under another
 * record of the SAME object by matching `record[parentField]` against the
 * sibling ids. `duly_duty` has no self-reference — its lookups point at
 * `sys_business_unit`, `duly_catalog_item` and a user — so a `type: 'tree'`
 * view here resolves no parent for any row, puts every duty at depth 0 and
 * renders a FLAT list. The renderer never reads `grouping`, so declaring
 * the two levels alongside it would change nothing, and nothing in
 * `pnpm validate` says so: the `view/layout-without-binding` gate does not
 * cover `tree` at all. That is the exact "renders wrong while authoring
 * reports success" shape this app's views exist to avoid, so it is not
 * shipped and the gap is filed upstream instead (see the PR body).
 *
 * The grid's grouping hook is the honest expression of the same idea and
 * it is measured, not assumed: it recurses through `grouping.fields`,
 * building nested `subgroups` with per-level collapse — a real two-level
 * hierarchy. Group keys sort by LABEL, never by bucket size, so no team
 * and no person is ever ordered by how much they owe.
 */
 catalog_tree: {
 label: 'What each team owes',
 type: 'grid',
 data,
 columns: [
 { field: 'name' },
 { field: 'form' },
 { field: 'frequency' },
 { field: 'source' },
 { field: 'status' },
 ],
 grouping: {
 fields: [{ field: 'business_unit' }, { field: 'owner' }],
 },
 sort: [{ field: 'name', order: 'asc' }],
 },
 },
});

131 changes: 131 additions & 0 deletions
src/views/task.view.ts

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -161,5 +161,136 @@ export const TaskViews = defineView({
 },
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Kanban. Columns come from `duly_task.status` — the renderer reads the
 * field's own `options` for the column set, their order and their labels
 * (measured in the console's `plugin-kanban`), so the board cannot drift
 * from the object.
 *
 * Dragging a card writes ONE field. Measured against the renderer's move
 * handler: `dataSource.update(object, id, { [groupBy]: toColumnId })` —
 * `status` and nothing else, which is the same write the row action does.
 * It is NOT gated on `inlineEdit`; it is gated on update permission, so a
 * user who may not write `status` gets the platform's rejection rather
 * than a silent no-op.
 *
 * `inlineEdit` is still declared, and it is not decoration: the toolbar
 * lets a viewer switch this view to its grid visualisation, and the
 * adapter honours `inlineEdit` on that branch (`editable:` is set in the
 * grid case only). On the kanban branch itself it is inert.
 *
 * No `summarizeField`: it renders a per-column SUM, and there is no number
 * on a task worth totalling. The nearest candidate would be a count, and
 * counts are never ranked or compared here.
 */
 board: {
 label: 'Board',
 type: 'kanban',
 data,
 columns: [{ field: 'subject' }, { field: 'due_date' }, { field: 'owner' }, { field: 'source' }],
 kanban: {
 groupByField: 'status',
 // The card face, in reading order: what it is, when it is owed, whose
 // it is, and where it came from.
 columns: ['subject', 'due_date', 'owner', 'source'],
 },
 inlineEdit: true,
 sort: [{ field: 'due_date', order: 'asc' }],
 },

 /**
 * Gantt. The bar runs `visible_from` → `due_date`, and that span IS the
 * lead time: a bar that starts on its own due date is a task that first
 * appeared the day it was already owed, which is a report on a failure
 * rather than a reminder. `lead_days` on the duty is what produces the
 * length, and this is the only screen where you can see it.
 *
 * Grouped by owner so an overloaded fortnight is visible as one person's
 * row going solid, before the period arrives.
 *
 * The filter is not a scope narrowing, it is a correctness one: the
 * renderer maps a missing date to `new Date()`, so an undated one-off
 * would draw a zero-width bar on TODAY and read as load that does not
 * exist. Both columns are stored and indexed; the unary operators carry
 * their direction in the name and take no value.
 *
 * No `colorField`, deliberately, and this is measured rather than an
 * oversight: the gantt renderer passes `record[colorField]` straight into
 * `backgroundColor`, so `colorField: 'status'` sets `background: "open"` —
 * not a colour, silently dropped, every bar identical. With the key
 * ABSENT the same renderer falls through to its status-derived palette and
 * the bars separate by state. Filed upstream; see the PR body.
 */
 schedule: {
 label: 'Schedule',
 type: 'gantt',
 data,
 columns: [
 { field: 'subject' },
 { field: 'status' },
 { field: 'owner' },
 { field: 'visible_from' },
 { field: 'due_date' },
 ],
 gantt: {
 startDateField: 'visible_from',
 endDateField: 'due_date',
 titleField: 'subject',
 groupByField: 'owner',
 viewMode: 'week',
 tooltipFields: [{ field: 'status' }, { field: 'period_key' }, { field: 'source' }],
 },
 filter: [
 { field: 'visible_from', operator: 'is_not_null' },
 { field: 'due_date', operator: 'is_not_null' },
 ],
 sort: [{ field: 'visible_from', order: 'asc' }],
 },

 /**
 * Timeline — the visual companion to `stalled`. Ordered by
 * `last_update_at`, which `task.hook.ts` stamps on a status change or a
 * note edit and deliberately does NOT advance on an administrative write,
 * so this really is "what has been happening" and not "what has been
 * touched".
 *
 * `colorField` earns its place here: the timeline renderer resolves it
 * against the object's own `status` options and uses the AUTHORED colours
 * (`#35674D` for done, and so on), so this lens and the status badge in
 * every grid read the same.
 */
 recent: {
 label: 'Recent activity',
 type: 'timeline',
 data,
 columns: [{ field: 'subject' }, { field: 'status' }, { field: 'owner' }, { field: 'last_update_at' }],
 timeline: {
 startDateField: 'last_update_at',
 titleField: 'subject',
 colorField: 'status',
 scale: 'day',
 },
 sort: [{ field: 'last_update_at', order: 'desc' }],
 },

 /**
 * The same rows a manager already reads, bucketed by team. `business_unit`
 * is denormalised onto the task at dispatch precisely so a rollup like
 * this survives a later transfer.
 *
 * Groups sort by LABEL — measured in the grid's grouping hook, which sorts
 * group keys with a locale compare on the label and never on the bucket
 * size. Nothing here ranks a unit, or a person, by a count.
 */
 by_unit: {
 label: 'By business unit',
 type: 'grid',
 data,
 columns,
 grouping: { fields: [{ field: 'business_unit' }] },
 bulkActionDefs: bulkActions,
 sort: [{ field: 'due_date', order: 'asc' }],
 },
 },
});
Loading
Loading