m/paliad
1
0
Fork 0
Code Issues 151 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

Feature: Verlauf — collapsible sections + asc/desc sort #34

New Issue
Open
opened 2026-05-09 16:35:30 +00:00 by mAi · 0 comments
mAi commented 2026-05-09 16:35:30 +00:00
Collaborator
Copy Link

Source: m @ 2026-05-09 18:32: "I would prefer if the different sections of the Verlauf would be collapsible and if we could further sort asc or desc."

Scope

Two small UX additions to the SmartTimeline (Verlauf tab on /projects/<id>):

  1. Collapsible sections. The timeline already has natural sections (past actuals / Heute / future projected; track sub-headers when CCR present; lane sub-headers at parent levels). Each section header gets a collapse toggle (chevron). Default state: all expanded. Collapsed state persists in localStorage per (project, section).

  2. Asc / desc sort toggle. Header chip pair: Älteste zuerst / Neueste zuerst. Default depends on whether the user is past- or future-leaning (mirrors riemann's macro chip pair from Slice 2). Asc/desc applies within each section after collapse handling.

Out of scope

  • Custom sort by field (e.g. by rule_code, by status). Asc/desc by date only.
  • Section-grouping changes (sections themselves stay as-is from Slice 1-4).

Acceptance

  • Each section header has a collapse chevron; clicking toggles section visibility.
  • Sort chip pair flips direction; preserves filter state.
  • Both states persist in localStorage per project.
  • Mobile (≤640px): same affordances, touch-target sized.

Filed by maria/paliad-head autonomously.

**Source:** m @ 2026-05-09 18:32: "I would prefer if the different sections of the Verlauf would be collapsible and if we could further sort asc or desc." ## Scope Two small UX additions to the SmartTimeline (Verlauf tab on `/projects/<id>`): 1. **Collapsible sections.** The timeline already has natural sections (past actuals / Heute / future projected; track sub-headers when CCR present; lane sub-headers at parent levels). Each section header gets a collapse toggle (chevron). Default state: all expanded. Collapsed state persists in localStorage per (project, section). 2. **Asc / desc sort toggle.** Header chip pair: `Älteste zuerst` / `Neueste zuerst`. Default depends on whether the user is past- or future-leaning (mirrors riemann's macro chip pair from Slice 2). Asc/desc applies within each section after collapse handling. ## Out of scope - Custom sort by field (e.g. by rule_code, by status). Asc/desc by date only. - Section-grouping changes (sections themselves stay as-is from Slice 1-4). ## Acceptance - Each section header has a collapse chevron; clicking toggles section visibility. - Sort chip pair flips direction; preserves filter state. - Both states persist in localStorage per project. - Mobile (≤640px): same affordances, touch-target sized. Filed by maria/paliad-head autonomously.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
deferred
Parked — not pursuing now, may un-park later
done
Work completed by an agent; awaiting m to close
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
mAi m
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: m/paliad#34
No description provided.
Delete Branch "%!s()"

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?