stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Share a privacy-reviewed summary after mobile Today wrap-up #1090

New Issue
Closed
opened 2026-08-18 18:22:17 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-18 18:22:17 +00:00
Member
Copy Link

Problem

The mobile Today journey saves actuals and schedules unfinished work, then stops at an internal status message. Operators must reconstruct a teammate-ready progress update from multiple screens.

Evidence

  • frontend/today-recap.js already has reviewed item titles, context, and actual minutes.
  • frontend/today-wrap-up.js already knows the exact tomorrow selections, but completion only closes the sheet.
  • Searches across all historical issue titles and recent commit subjects found no standup/daily-summary/share-recap implementation.

Product slice

After wrap-up, open a privacy review sheet containing worked-on and tomorrow items. Actual time is excluded by default. Let the operator edit a bounded note, choose rows, then use the native share sheet with a clipboard fallback. Keep a private account-scoped draft until sharing succeeds or the operator discards it.

Acceptance tests

  • Recap + wrap-up opens a summary with exact worked-on and tomorrow selections.
  • Rows are selectable; actual time is opt-in and excluded by default.
  • Draft survives close/reload only for the current normalized login and is purged on discard/sign-out private-data cleanup.
  • Native share receives deterministic plain text; unsupported share uses one clipboard write; canceled share remains a draft and never claims success.
  • 320x568 and 390x844 render 44px actions with no horizontal overflow.
  • Existing recap, time logging, and tomorrow scheduling remain green.
## Problem The mobile Today journey saves actuals and schedules unfinished work, then stops at an internal status message. Operators must reconstruct a teammate-ready progress update from multiple screens. ## Evidence - `frontend/today-recap.js` already has reviewed item titles, context, and actual minutes. - `frontend/today-wrap-up.js` already knows the exact tomorrow selections, but completion only closes the sheet. - Searches across all historical issue titles and recent commit subjects found no standup/daily-summary/share-recap implementation. ## Product slice After wrap-up, open a privacy review sheet containing worked-on and tomorrow items. Actual time is excluded by default. Let the operator edit a bounded note, choose rows, then use the native share sheet with a clipboard fallback. Keep a private account-scoped draft until sharing succeeds or the operator discards it. ## Acceptance tests - Recap + wrap-up opens a summary with exact worked-on and tomorrow selections. - Rows are selectable; actual time is opt-in and excluded by default. - Draft survives close/reload only for the current normalized login and is purged on discard/sign-out private-data cleanup. - Native share receives deterministic plain text; unsupported share uses one clipboard write; canceled share remains a draft and never claims success. - 320x568 and 390x844 render 44px actions with no horizontal overflow. - Existing recap, time logging, and tomorrow scheduling remain green.
timmy was assigned by rockachopa 2026-08-18 18:22:17 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#1090
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?