-
Notifications
You must be signed in to change notification settings - Fork 1
feat: name Weekly VOC and focus Event Lineage (v2.13.0) #260
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.
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
Changes from all commits
c107d1f
0dd2804
f4a5b55
debd51b
b6c3b02
0d756b6
86fa07b
a6b87a6
ffffd2d
043505c
f960ee9
ed2282b
d208529
4fdd027
49f99dc
4dfde04
f5de56d
c0e9043
868559e
74718d6
3bcea53
79545af
431a642
727512a
0f93b03
1f2cb3f
9b61751
dfd95d9
7b5c1e9
e573875
8268b14
6f31284
1f905a3
aeb0d93
294fe99
c518058
8ef98a0
b7625c3
d58651e
643338a
6a1177d
a9d0462
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| # 2.12.0 Weekly VOC ISO-week list filter | ||
|
|
||
| Weekly VOC on Board keeps Voice of Customer posts for the latest ISO-8601 | ||
| week (UTC Thursday rule). Other VOC types and older weeks drop out. The | ||
| Board names Event Lineage as the next read. No TEPP theta is invented. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| # 2.13.0 Opening Weekly VOC focuses Event Lineage | ||
|
|
||
| Open a Voice of Customer post from an active Weekly VOC filter and the | ||
| popup Event Lineage heading takes focus. The popup names that post as | ||
| current and to read Keyman and evaluation next. Home-list opens do not. | ||
| No TEPP theta is invented. |
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 📝 Info: list_posts SQL parameter renumbering is fully consistent The insertion of Was this helpful? React with 👍 or 👎 to provide feedback. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| # ADR 0092: Weekly VOC is an ISO-8601 week list filter | ||
|
devin-ai-integration[bot] marked this conversation as resolved.
|
||
|
|
||
| - Status: Accepted | ||
| - Date: 2026-08-19 | ||
|
|
||
| ## Context | ||
|
|
||
| Board already exposes checkbox VOC-type filters (ADR 0060). Buyers still need | ||
| one named control that shows this week's Voice of Customer posts without | ||
| inventing a measurement or collapsing other VOC types into a guessed default. | ||
| PR #259 stacked a `<select>` week filter on a stale Board that used a single | ||
| string type filter; current Board keeps `typeFilter` as `string[]`. | ||
|
|
||
| ## Decision | ||
|
|
||
| Weekly VOC is a Board list filter, not a report and not ADR 0051 named hints. | ||
|
|
||
| - The **Weekly VOC** control sets VOC type to `voc` only and selects the | ||
| latest ISO-8601 week (`YYYY-Www`) present among authorized Voice of | ||
| Customer posts. | ||
| - Week membership uses the UTC date of `created_at`. Thursday decides the | ||
| ISO week-year (ISO 8601 week date). | ||
| - An explicit ISO-week `<select>` remains available beside the named | ||
| control. Reset filters returns both the checkboxes and the week to All. | ||
| - The Board names the next action: Voice of Customer posts for that week | ||
| are current; open a post to read Event Lineage. | ||
| - No TEPP theta is invented. No cutoff body is invented (ADR 0016). | ||
|
|
||
| ## Consequences | ||
|
|
||
| - Weekly VOC composes with the existing checkbox VOC vocabulary instead of | ||
| replacing it. | ||
| - Posts whose `created_at` cannot be parsed contribute no week and cannot | ||
| be selected by this filter. | ||
| - Home-list and Customer-master opens are unchanged until ADR 0093. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| # ADR 0093: Opening a Weekly VOC post focuses Event Lineage | ||
|
|
||
| - Status: Accepted | ||
| - Date: 2026-08-19 | ||
|
|
||
| ## Context | ||
|
|
||
| ADR 0092 names Weekly VOC as an ISO-week list filter and tells the buyer to | ||
| open a post to read Event Lineage. Report-member opens already focus the | ||
| popup Event Lineage heading. A home-list open must not steal that focus or | ||
| add that next-action copy. | ||
|
|
||
| ## Decision | ||
|
|
||
| Opening a Board post while Weekly VOC is active (`voc` only and a concrete | ||
| ISO week) is a `fromWeeklyVoc` open. That open reuses the existing Event | ||
| Lineage focus path used by report-member opens: | ||
|
|
||
| - The popup Event Lineage heading takes focus. | ||
| - The popup names the opened post as current in Event Lineage and tells | ||
| the buyer to read Keyman and evaluation next. | ||
|
|
||
| A Board open from the unfiltered home list, a reset filter list, or any | ||
| path that did not set `fromWeeklyVoc` does not focus Event Lineage and | ||
| does not add that copy. Closing the popup clears the Weekly VOC open flag. | ||
|
|
||
| No TEPP theta is invented. No cutoff body is invented (ADR 0016). | ||
|
|
||
| ## Consequences | ||
|
|
||
| - Weekly VOC and report-member opens share one focus contract. | ||
| - Changing VOC checkboxes or the ISO week so Weekly VOC is no longer | ||
| active makes the next Board open a home-list open. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📝 Info: CHANGELOG version/date ordering is non-monotonic
In CHANGELOG.md, the new
## [2.13.0] - 2026-08-19and## [2.12.0] - 2026-08-19sections are placed above## [Unreleased], and## [2.11.0]/## [2.10.0](both dated 2026-08-18) are inserted between## [2.12.6] - 2026-08-20and## [2.12.5] - 2026-08-18. The version numbers and dates no longer decrease monotonically down the file. This is a documentation ordering inconsistency (Keep a Changelog normally keeps [Unreleased] at the top and released versions in descending order), not a functional defect.Was this helpful? React with 👍 or 👎 to provide feedback.