Show staff what changed after an update closes #683 #692
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
local-it/mitgliederverwaltung!692
Loading…
Reference in a new issue
No description provided.
Delete branch "issue/mitgliederverwaltung-683"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
closes #683
Description of the implemented changes
The changes were:
Staff now see what changed in Mila on a page "What's new", reached from an entry right above the sidebar footer. The page lists the changes of the last five releases that concern the person's role, newest first, each with a link to the exact place it is about. A change that asks someone to act is a task: it is marked "Open", counted on the sidebar entry ("2 open", a number on the icon when the sidebar is collapsed) and shown as a hint at its place ("New: …" with "All news" and "Done") until the person marks it as done, one by one or all at once with "Undo". Unread changes without a task are counted as "N new" until the page is opened. Members do not see any of it.
Each release's changes are a data file (
priv/whats_new/<version>.exs), read and checked at compile time: literals only, at most five entries, unique ids, known areas and permission sets, a task needs a link, a hint needs a task. This PR ships the files for 1.5.0 and 1.6.0 and the rule for writing them (docs/whats-new.md, a step indocs/releasing.md).What has been changed?
Definition of Done
Code Quality
Accessibility
Testing
Additional Notes
users.whats_new_since,whats_new_seen_version,whats_new_done): the migration starts existing accounts at 1.4.0, so 1.5.0 and 1.6.0 show as new once; new accounts start at the running version. Only a release build shows anything as new or open; a development build and a downgrade show nothing.Mv.WhatsNew.Visibilitybehaviour (configured like:join_notifier). Done and Undo compute the list from the stored row, locked in the action's transaction, so two tabs or devices keep each other's done tasks. Forged ids, another person's state and members are refused (tests send them).MvWeb.WhatsNewHint) keeps the hint for the current path and handles its "Done" on every page; a page shows it with<.whats_new_hint>where the task's link lands. A data test fails for a hint no page shows.<.callout>gainedtitleandactionsfor it (showcase variant added).scroll-padding-toponhtmlnever saw the top bar height (the variable was declared on a descendant), so every#sectionlink put the heading under the sticky bar; fixed on its own commit. Every jump now focuses the section's heading and outlines it for about 3 s (no fade with reduced motion). There is no browser test layer; this was checked in Chromium and Firefox, desktop and phone.<.modal kind={:view}>: only Close, backdrop closes, wide enough for a 600 px email); a note below both cards replaces the info callout.indicator,badgeandstatus(DESIGN_GUIDELINES §21.2); the hand-positioned.nav-countis gone.The CHANGELOG has an upgrade note: existing accounts start at 1.4.0 and see 1.5.0 and 1.6.0 as new; admins and the board have one open task each.
Proposed news entry: none for this feature. The newest data file in this PR already holds five entries (the limit), all about changes that ask something of a role; "What's new" introduces itself through its sidebar count on the first sign-in after the update.