2026-06-06 19:29:25 +03:00
|
|
|
|
# KisaniCal — Issue Tracker
|
|
|
|
|
|
|
|
|
|
|
|
Status legend: `Open` · `In Progress` · `Resolved`
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-1 — Daily workout log does not reset on a new day
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (fix implemented & tested locally, pending release)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Workout
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
When the same workout program is scheduled on back-to-back days (e.g. Shoulders
|
|
|
|
|
|
on Monday **and** Tuesday), the new day does not start fresh. Completed sets from
|
|
|
|
|
|
the previous day stay checked, so the workout appears already done.
|
|
|
|
|
|
|
|
|
|
|
|
### Root cause
|
|
|
|
|
|
Set completion (`ExerciseSet.isDone`) was stored permanently inside the
|
|
|
|
|
|
`WorkoutProgram` and persisted via `save()`. There was no per-day reset, so a
|
|
|
|
|
|
program reused the next day carried over yesterday's checkmarks.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
Set completion is now a per-day state:
|
|
|
|
|
|
- `WorkoutViewModel.resetSetsForNewDayIfNeeded()` clears every set's `isDone`
|
|
|
|
|
|
across all programs when the calendar day changes (skips first launch, no-ops
|
|
|
|
|
|
when the day is unchanged).
|
|
|
|
|
|
- `toggleSet(...)` stamps the active day so on-screen state always belongs to today.
|
|
|
|
|
|
- Called on cold launch (`init`), `.onAppear`, and `scenePhase == .active`
|
|
|
|
|
|
(handles crossing midnight while the app is alive).
|
|
|
|
|
|
- Streak history (`workoutDates`) is untouched, so completed days still count.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `KisaniCal/Models/ExerciseModels.swift`, `KisaniCal/ContentView.swift`
|
|
|
|
|
|
|
|
|
|
|
|
### Verification
|
2026-06-06 19:29:25 +03:00
|
|
|
|
Builds cleanly (Xcode 26.2 SDK, simulator). Verified in-process on the simulator
|
|
|
|
|
|
via the real `resetSetsForNewDayIfNeeded()` against a seeded completed set:
|
|
|
|
|
|
`before=[true] after=[false] day=2026-06-06 -> PASS`. Streak preserved.
|
|
|
|
|
|
Committed in `cdc46e9`.
|
2026-06-06 19:29:25 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-2 — App logo update (new KisaniCal brand mark)
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (assets installed & build-verified, pending release)
|
|
|
|
|
|
**Area:** Branding / App Icon
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
Replace the app icon with the new KisaniCal logo (orange dot grid on dark) across
|
|
|
|
|
|
the App Store marketing icon and all home/lock screen / Spotlight / notification sizes.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
All 12 sizes in `AppIcon.appiconset` regenerated from the new source. Alpha
|
|
|
|
|
|
flattened onto the brand dark background `RGB(26,29,34)` so the 1024 App Store icon
|
|
|
|
|
|
is fully opaque (App Store Connect compliant) and device icons are full-bleed.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `KisaniCal/Assets.xcassets/AppIcon.appiconset/`
|
|
|
|
|
|
|
|
|
|
|
|
### Verification
|
2026-06-06 19:29:25 +03:00
|
|
|
|
Builds cleanly (app + widget extension); `hasAlpha: no` on all icons. New logo
|
|
|
|
|
|
confirmed compiled into `Assets.car` (home, lock-screen notification, Spotlight,
|
|
|
|
|
|
Settings all derive from `AppIcon`). Committed in `cdc46e9`.
|
|
|
|
|
|
Note: device still shows old icon until the new build is installed (delete + reinstall).
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-3 — Today view: section order + RSS feeds leaking into Tasks
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified, pending release)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Tasks / Today
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
Two changes to the Today view:
|
|
|
|
|
|
1. The Overdue card sat at the very top, above today's active tasks. Active tasks
|
|
|
|
|
|
should always be the top section.
|
|
|
|
|
|
2. Subscribed/RSS calendar feeds (F1 schedule, TV-show calendars) were appearing
|
|
|
|
|
|
in the Today/Tasks timeline. They belong in the Calendar tab only.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- Moved the `OverdueCard` to render directly below today's active tasks (above
|
|
|
|
|
|
Next 3 Days), so active tasks stay at the top.
|
|
|
|
|
|
- `todayCalEvents` now excludes events whose `calendar.type == .subscription`, so
|
|
|
|
|
|
RSS/ICS feeds are filtered out of the Today timeline. The Calendar view reads
|
|
|
|
|
|
`monthEvents` directly and is unaffected.
|
|
|
|
|
|
- Birthdays (`.birthday`) and personal/CalDAV calendars are intentionally left
|
|
|
|
|
|
visible; the existing per-calendar visibility toggle (`hiddenCalendarIDs`) lets
|
|
|
|
|
|
the user hide any of them. User-created tasks are never affected.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `KisaniCal/Views/TodayView.swift`
|
|
|
|
|
|
|
|
|
|
|
|
### Verification
|
2026-06-06 19:46:39 +03:00
|
|
|
|
Builds cleanly. Committed in `f66f032` (re-authored `a92e9d4`).
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-4 — Unified task context menu + Live Activity + calendar event actions
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified; Live Activity pending on-device test)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Tasks / Calendar / Widgets
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
Long-pressing a task (in any task list) should show a consistent menu:
|
|
|
|
|
|
Pin · Date · Move · Priority · Tags · Add to Live Activity · Delete — and the
|
|
|
|
|
|
actions must actually work. Long-pressing a non-subscription calendar event
|
|
|
|
|
|
should offer Edit / Delete only.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- New shared `TaskMenuItems` (KisaniCal/Views/TaskContextMenu.swift) used by the
|
|
|
|
|
|
Today timeline, Matrix (grid + Overdue/Later/Completed lists), and Calendar
|
|
|
|
|
|
day timeline. Added `TaskViewModel.setPriority`.
|
|
|
|
|
|
- Live Activity (ActivityKit): `TaskActivityAttributes` (shared app+widget),
|
|
|
|
|
|
`LiveActivityManager` (start/update/end/toggle, iOS 16.1+), `TaskLiveActivity`
|
|
|
|
|
|
widget (lock screen + Dynamic Island), `NSSupportsLiveActivities` via project.yml.
|
|
|
|
|
|
- Calendar events (non-subscription, writable only): Edit opens the system
|
|
|
|
|
|
`EKEventEditViewController` (`EventEditView`); Delete via `CalendarStore.deleteEvent`.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `TaskContextMenu.swift`, `TaskActivityAttributes.swift`,
|
|
|
|
|
|
`LiveActivityManager.swift`, `TaskLiveActivity.swift`, `TaskItem.swift`,
|
|
|
|
|
|
`MatrixView.swift`, `CalendarView.swift`, `TodayView.swift`,
|
|
|
|
|
|
`KisaniCalWidgets.swift`, `project.yml`. Committed in `d0d982f`.
|
|
|
|
|
|
|
|
|
|
|
|
### How to test
|
|
|
|
|
|
1. **Menu parity** — long-press a task in Today, in a Matrix quadrant, in a
|
|
|
|
|
|
Matrix list (Overdue/Later), and in the Calendar day view. All show the same
|
|
|
|
|
|
7 items.
|
|
|
|
|
|
2. **Each action** — Pin (row pins), Date → Today/Tomorrow/Next Week/Remove
|
|
|
|
|
|
(due date changes), Move (task changes quadrant), Priority (flag changes),
|
|
|
|
|
|
Tags (category changes), Delete (removed).
|
|
|
|
|
|
3. **Live Activity** — tap "Add to Live Activity" → a banner appears on the Lock
|
|
|
|
|
|
Screen / Dynamic Island with the task title + countdown; tap again to end.
|
|
|
|
|
|
**Requires a real iOS 16.1+ device** (not visible in the Simulator).
|
|
|
|
|
|
4. **Calendar events** — long-press a personal (writable) event → Edit opens the
|
|
|
|
|
|
system editor; Delete removes it. A subscribed/RSS event (F1, TV) shows **no**
|
|
|
|
|
|
menu.
|
|
|
|
|
|
|
|
|
|
|
|
### Known limitations
|
|
|
|
|
|
- Live Activity visuals only render on a physical device; the design is a first
|
|
|
|
|
|
pass (orange accent + timer) and can be refined.
|
|
|
|
|
|
- Uses the iOS 16.1 `Activity.request(...contentState:...)` API (deprecation
|
|
|
|
|
|
warning on 16.2+, still functional).
|
2026-06-07 04:08:23 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-5 — Calendar "Connect" toggle unreliable / inconsistent across screens
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified; full reliability win is device-only)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Calendar / Permissions
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
The iPhone Calendar "Connect" sometimes needed repeated taps, onboarding
|
|
|
|
|
|
sometimes didn't reflect a granted calendar, and there was no place to see/manage
|
|
|
|
|
|
connection status from Settings.
|
|
|
|
|
|
|
|
|
|
|
|
### Root cause
|
|
|
|
|
|
Three independent calendar-permission states that never synced: `TodayView`,
|
|
|
|
|
|
`CalendarView` each had their own `CalendarStore` + `EKEventStore`, and
|
|
|
|
|
|
`OnboardingView` had its own raw `EKEventStore`. Granting in one left the others
|
|
|
|
|
|
showing stale cached status until they happened to re-read it.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- `CalendarStore.shared` singleton — one source of truth used by Today, Calendar,
|
|
|
|
|
|
Onboarding, and Settings. Connect once, every screen reflects it.
|
|
|
|
|
|
- `requestAccess()` now debounces in-flight requests and reads the **authoritative**
|
|
|
|
|
|
`EKEventStore.authorizationStatus` instead of trusting the callback bool;
|
|
|
|
|
|
already-decided states re-sync via `refreshStatus()`.
|
|
|
|
|
|
- Turning on "Show Calendar Events" while unauthorized now triggers the prompt.
|
|
|
|
|
|
- New **Settings → Data → Calendar** row showing ● Connected / Connect / Denied,
|
|
|
|
|
|
opening the connect sheet.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `CalendarView.swift`, `TodayView.swift`, `OnboardingView.swift`,
|
|
|
|
|
|
`SettingsView.swift`.
|
|
|
|
|
|
|
|
|
|
|
|
### Verification
|
|
|
|
|
|
Builds cleanly. Cross-screen consistency + the Settings status row are testable in
|
|
|
|
|
|
the Simulator; the request-reliability fix is best confirmed on a device.
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-6 — No notifications for calendar events
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified; fires on a real device with calendar access)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Calendar / Notifications
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
Task reminders fired, but calendar events never produced a KisaniCal
|
|
|
|
|
|
notification — events with no iOS alert (e.g. subscribed F1/TV feeds) notified
|
|
|
|
|
|
the user of nothing.
|
|
|
|
|
|
|
|
|
|
|
|
### Root cause
|
|
|
|
|
|
`NotificationManager` only scheduled workout + per-task notifications. There was
|
|
|
|
|
|
no calendar-event path at all (`EKEvent`/`CalendarStore` were never involved).
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- `CalendarStore.upcomingEventNotifs(days:)` snapshots visible events for the next
|
|
|
|
|
|
7 days (respects enabled flag + hidden calendars) with start time + alarm offsets.
|
|
|
|
|
|
- `NotificationManager.scheduleCalendarEvents(...)` schedules a notification at the
|
|
|
|
|
|
event start ("on time") plus at each alarm the user set; all-day events fire at
|
|
|
|
|
|
9am morning-of. Capped at ~20 to stay under iOS's 64 pending-notification limit;
|
|
|
|
|
|
recurring instances kept unique via start-time in the id.
|
|
|
|
|
|
- Wired into `reschedule(...)` (runs on foreground / scene-active / task changes).
|
|
|
|
|
|
|
|
|
|
|
|
Files: `CalendarView.swift`, `NotificationManager.swift`.
|
|
|
|
|
|
|
|
|
|
|
|
### How to test (device, calendar access granted)
|
|
|
|
|
|
1. Create an event a few minutes out with **no alert** on a visible calendar.
|
|
|
|
|
|
2. Background the app (triggers a reschedule).
|
|
|
|
|
|
3. Notification fires at the event's start time.
|
|
|
|
|
|
|
|
|
|
|
|
### Known limitations / decisions
|
|
|
|
|
|
- "All visible events" was chosen, so personal events that already have an iOS
|
|
|
|
|
|
alert may double (system + KisaniCal). Feed events (F1/TV) are the main win.
|
|
|
|
|
|
- Tapping a calendar notification opens the Today view (no calendar deeplink).
|
|
|
|
|
|
- The 7-day window re-scans on each foreground; no background refresh beyond that.
|
2026-06-07 14:11:26 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-7 — App Store upload: "iPad Multitasking must provide a launch screen"
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** Resolved (fix in `72f4566`; re-archive required to ship)
|
|
|
|
|
|
**Reported by:** User (App Store / Transporter validation)
|
|
|
|
|
|
**Area:** Build / App Store
|
|
|
|
|
|
|
|
|
|
|
|
### Symptom
|
|
|
|
|
|
Upload fails validation:
|
|
|
|
|
|
> Invalid bundle. Apps that support Multitasking on iPad must provide the app's
|
|
|
|
|
|
> launch screen using an Xcode storyboard, or using UILaunchScreen … Verify that
|
|
|
|
|
|
> the UILaunchStoryboardName key is included in your com.kutesir.KisaniCal bundle.
|
|
|
|
|
|
|
|
|
|
|
|
### Root cause
|
|
|
|
|
|
The app targets iPad (`TARGETED_DEVICE_FAMILY = "1,2"`) with multitasking
|
|
|
|
|
|
(`UIApplicationSupportsMultipleScenes = true`), but `project.yml` had
|
|
|
|
|
|
`INFOPLIST_KEY_UILaunchStoryboardName: ""` (empty) and no `UILaunchScreen` —
|
|
|
|
|
|
so the bundle shipped no valid launch screen.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- Added `KisaniCal/LaunchScreen.storyboard` (blank, `systemBackgroundColor`).
|
|
|
|
|
|
- `project.yml`: `INFOPLIST_KEY_UILaunchStoryboardName: LaunchScreen`.
|
|
|
|
|
|
- `xcodegen generate`. Verified a clean **Release** build emits
|
|
|
|
|
|
`UILaunchStoryboardName = LaunchScreen` and ships `LaunchScreen.storyboardc`.
|
|
|
|
|
|
|
|
|
|
|
|
### ⚡ If it happens again — solve it fast
|
|
|
|
|
|
This error almost always recurs because a **stale archive** was uploaded, NOT
|
|
|
|
|
|
because the code is wrong. Checklist:
|
|
|
|
|
|
1. Confirm the fix is present:
|
|
|
|
|
|
`grep UILaunchStoryboardName project.yml` → must be `LaunchScreen` (not `""`).
|
|
|
|
|
|
`git log --oneline -- KisaniCal/LaunchScreen.storyboard` → should show `72f4566`.
|
|
|
|
|
|
2. If Xcode was open, **reload the project** (xcodegen rewrites `.xcodeproj`).
|
|
|
|
|
|
3. **Product → Clean Build Folder (⇧⌘K)** — a cached build folder re-emits the old
|
|
|
|
|
|
Info.plist. This is the step people skip.
|
|
|
|
|
|
4. **Bump `CURRENT_PROJECT_VERSION`** in `project.yml` + `xcodegen generate`
|
|
|
|
|
|
(a failed upload can "use up" the build number).
|
|
|
|
|
|
5. Re-Archive → Validate → Distribute.
|
|
|
|
|
|
6. Sanity check any archive:
|
|
|
|
|
|
`/usr/libexec/PlistBuddy -c "Print :UILaunchStoryboardName" <App>.app/Info.plist`
|
|
|
|
|
|
and `ls <App>.app | grep LaunchScreen` (expect `LaunchScreen.storyboardc`).
|
|
|
|
|
|
|
|
|
|
|
|
Committed: fix `72f4566`, build-number bump `345415e`.
|
2026-06-07 23:12:46 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-8 — Workout doesn't follow the schedule; rest day shows a stale workout
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified, pending device build)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Workout
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
The Workout tab kept showing the last-used program with its old completion,
|
|
|
|
|
|
ignoring the weekly schedule. On a rest day (no program assigned) it still
|
|
|
|
|
|
displayed a fully-checked workout from a previous day.
|
|
|
|
|
|
|
|
|
|
|
|
### Root cause
|
|
|
|
|
|
The daily reset (KC-1) cleared set completion but never changed the **active
|
|
|
|
|
|
program** — it stayed on whatever was last selected, regardless of the schedule.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- `applyScheduledProgramForToday()` (run from `resetSetsForNewDayIfNeeded` on a
|
|
|
|
|
|
new day) switches the active program to the one assigned to today.
|
|
|
|
|
|
- `isRestDayToday` (schedule exists but today has no entry) drives a new **Rest
|
|
|
|
|
|
Day** card in `WorkoutView` with a "Work out anyway" override; header reads
|
|
|
|
|
|
"Rest Day".
|
|
|
|
|
|
- Daily set reset (KC-1) unchanged.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `ExerciseModels.swift`, `WorkoutView.swift`. Committed in `f9081cf`.
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-9 — Per-day workout history
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified, pending device build)
|
|
|
|
|
|
**Reported by:** User ("store the data for each day")
|
|
|
|
|
|
**Area:** Workout
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
Set completion resets daily, so there was no way to look back at what was
|
|
|
|
|
|
actually logged on a past day.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- New `WorkoutDayLog` / `LoggedExercise` / `LoggedSet` models; stored as
|
|
|
|
|
|
`kisani.workout.history.<uid>` (and iCloud-synced).
|
|
|
|
|
|
- `snapshotDay(_:)` captures the active program's completed sets — called from
|
|
|
|
|
|
`logWorkoutCompleted` (same-day) and from the daily reset **before** wiping
|
|
|
|
|
|
(captures partial days). Only records days with ≥1 set done.
|
|
|
|
|
|
- New `WorkoutHistoryView` (clock button in the Workout header) lists past days
|
|
|
|
|
|
newest-first with program, sets done, and per-exercise breakdown.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `ExerciseModels.swift`, `WorkoutView.swift`.
|
2026-06-08 00:29:48 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-10 — Calendar marks future workouts complete (per-type, not per-date)
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified, pending device build)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Calendar / Workout
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
In the calendar, completing one occurrence of a program (e.g. Tuesday Shoulders)
|
|
|
|
|
|
showed **every** occurrence of that program as completed — including **future**
|
|
|
|
|
|
days (Saturday Shoulders) — with a checkmark + strikethrough.
|
|
|
|
|
|
|
|
|
|
|
|
### Root cause
|
|
|
|
|
|
`DayTimelineView` computed the workout's completion from the program's **live**
|
|
|
|
|
|
shared set state: `w.doneSets == w.totalSets`. `program(for: date)` returns the
|
|
|
|
|
|
same program object for every date it's scheduled, so its in-progress completion
|
|
|
|
|
|
leaked onto all of those dates.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- Added `WorkoutViewModel.isWorkoutComplete(on:)` — checks `workoutDates` (the set
|
|
|
|
|
|
of dates a workout was actually finished/Health-detected), i.e. **per-date**.
|
|
|
|
|
|
- `DayTimelineView` now takes a `workoutDone: Bool` and uses it instead of the live
|
|
|
|
|
|
`doneSets`. Calendar passes `isWorkoutComplete(on: selectedDate)`, Today passes
|
|
|
|
|
|
`isWorkoutComplete(on: today)`.
|
|
|
|
|
|
- Result: a date shows the workout complete only if that **specific date** was
|
|
|
|
|
|
finished. Future occurrences are never auto-completed.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `ExerciseModels.swift`, `CalendarView.swift`, `TodayView.swift`.
|
2026-06-09 01:41:15 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-11 — Calendar appeared capped at 2026 (no year shown)
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** Resolved
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Calendar
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
Users couldn't navigate/see dates beyond 2026.
|
|
|
|
|
|
|
|
|
|
|
|
### Root cause
|
|
|
|
|
|
Navigation was actually unbounded, but every header showed only the month name
|
|
|
|
|
|
(`"MMMM"`) — the Year view had no year label at all — so crossing a year boundary
|
|
|
|
|
|
was invisible and future months felt unreachable (compounded by empty future
|
|
|
|
|
|
months from the missing recurrence engine, KC-12).
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
Show the year: main header `"Month Year"`, date-picker grid `"MMMM yyyy"`, and a
|
|
|
|
|
|
`◀ year ▶` navigator + label in the Year view (`navigateYear`).
|
|
|
|
|
|
Files: `CalendarView.swift`, `TodayView.swift`. Committed in `7b2b61a`.
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-12 — Recurring tasks don't appear on future dates
|
|
|
|
|
|
|
2026-06-09 10:47:13 +03:00
|
|
|
|
**Status:** In Progress (implemented & build-verified, pending device build)
|
2026-06-09 01:41:15 +03:00
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Tasks / Calendar
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
A task set to repeat (Daily/Weekly/Monthly/Yearly/Every-Weekday) only ever showed
|
|
|
|
|
|
on its single original `dueDate`. No future occurrences, no per-occurrence
|
|
|
|
|
|
completion.
|
|
|
|
|
|
|
|
|
|
|
|
### Root cause
|
|
|
|
|
|
There was no recurrence engine — tasks carry `isRecurring` + `recurrenceLabel` but
|
|
|
|
|
|
a single `dueDate`, and every surface matched by `isDate(dueDate, inSameDayAs:)`.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix (core)
|
|
|
|
|
|
- Model: `recurrenceEnd` + `completedOccurrences` (optional → safe decode of old data).
|
|
|
|
|
|
- `TaskViewModel` engine: `isOccurrence(_:on:)`, `occurrenceComplete`,
|
|
|
|
|
|
`toggleOccurrence`, `occurrenceCopy`, `nextOccurrence`, `occurrences(on:)`.
|
|
|
|
|
|
- `toggle(_:)` routes recurring rows to per-occurrence completion (one day never
|
|
|
|
|
|
affects another).
|
|
|
|
|
|
- Date filters (`today`/`next3`/`upcoming`/`completedToday`) exclude recurring
|
|
|
|
|
|
masters and re-inject per-date occurrence copies; recurring never goes "overdue".
|
|
|
|
|
|
- Calendar dots + day detail use `occurrences(on:)`.
|
|
|
|
|
|
- Works across year boundaries; respects `recurrenceEnd` when set.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `TaskItem.swift`, `CalendarView.swift`.
|
|
|
|
|
|
|
2026-06-09 10:47:13 +03:00
|
|
|
|
### "Repeat until" UI (done)
|
|
|
|
|
|
- Added `recurrenceEnd` through `NLParsed`, `TaskDatePickerSheet`, both add/edit
|
|
|
|
|
|
sheets, and `addTask`/`updateTask`.
|
|
|
|
|
|
- Date picker shows a "Repeat until" row (graphical date picker, default "Forever",
|
|
|
|
|
|
with Clear) whenever a recurrence is selected.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `TaskItem.swift`, `CalendarView.swift`, `TodayView.swift`, `MatrixView.swift`.
|
2026-06-10 10:09:55 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-13 — Recurrence redesign: single occurrence, new sections, classic Matrix
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified, pending device build)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Tasks / Calendar / Matrix
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
The first recurrence pass used calendar-expansion in lists — a daily task showed
|
|
|
|
|
|
in Today, Tomorrow, Next 7 Days, and Upcoming simultaneously (planning noise).
|
|
|
|
|
|
Should behave like TickTick: one task, one next occurrence, one source of truth.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- **Single active occurrence (P1/P5):** `nextActiveOccurrence` + `activeRows` — each
|
|
|
|
|
|
recurring task contributes ONE row (its next un-completed occurrence). Completing
|
|
|
|
|
|
rolls forward; no future duplicates in lists. Calendar grid still shows per-date.
|
|
|
|
|
|
- **Sections (P2):** replaced Today / Next 3 Days / Upcoming with
|
|
|
|
|
|
**Today / Tomorrow / Next 7 Days / Later** (`todayTasks`/`tomorrowTasks`/
|
|
|
|
|
|
`next7DaysTasks`/`laterTasks`; `UpcomingSection` gained a `title`).
|
|
|
|
|
|
- **Icons (P3):** ⏰ reminder + 🔁 recurring on the right of each row; fixed the
|
|
|
|
|
|
hardcoded "Annual" label to show the real frequency.
|
|
|
|
|
|
- **Matrix (P4):** classic Eisenhower — importance is user-assigned (row), urgency is
|
|
|
|
|
|
derived from the deadline (within `urgentWindowDays` = 7). `displayQuadrant` +
|
|
|
|
|
|
`matrixTasks` group by the computed quadrant; recurring rolls forward. Chosen over
|
|
|
|
|
|
the fully-auto "far = Q4" model so the user keeps control of importance.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `TaskItem.swift`, `TodayView.swift`, `MatrixView.swift`.
|
|
|
|
|
|
Commits: `b4e36db` (lists + icons), `2f1bc5d` (Matrix).
|
2026-06-10 10:21:12 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-14 — Workout Stats (daily / weekly / monthly performance)
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified, pending device build)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Workout
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
Per-day logs (KC-9) existed but weren't aggregated, so there was no way to compare
|
|
|
|
|
|
daily/weekly/monthly performance.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- `WorkoutDayLog.volume` (Σ weight×reps over done sets); `StatPeriod`/`WorkoutStat`/
|
|
|
|
|
|
`StatBucket`.
|
|
|
|
|
|
- `WorkoutViewModel`: `stat(period, offset:)` (current vs previous), `statInterval`,
|
|
|
|
|
|
`statBuckets(period, count:)` for charting.
|
|
|
|
|
|
- New `WorkoutStatsView` (chart-bar button in the Workout header): Day/Week/Month
|
|
|
|
|
|
selector, summary cards (Workouts / Sets / Volume) with %-delta vs the previous
|
|
|
|
|
|
period, a metric chooser, and a Swift Charts bar trend (last 14 days / 8 weeks /
|
|
|
|
|
|
6 months). Empty state when no history.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `ExerciseModels.swift`, `WorkoutView.swift`.
|
|
|
|
|
|
|
|
|
|
|
|
### Note
|
|
|
|
|
|
Stats are computed from the app's own per-day logs. Health (steps/kcal/resting HR +
|
|
|
|
|
|
workout dates) is already read on the Today dashboard and merged into the streak;
|
|
|
|
|
|
a Health overlay on this screen could be added later.
|
2026-06-10 17:31:55 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-15 — Bars countdown widget + unified slate/orange widget theme
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified, pending device build)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Widgets
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
Add a bar-meter event-countdown widget (per reference screenshot) and re-theme
|
|
|
|
|
|
every widget to one look: dark slate background + brand orange, matching the app.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- `WidgetTheme` (slate background `RGB(0.224,0.255,0.31)`, brand orange accent).
|
|
|
|
|
|
- `BarGrid` vertical-bar progress view; new `EventBarsView` + `EventBarsWidget`
|
|
|
|
|
|
("Event Countdown (Bars)", medium) reusing the existing event config/provider.
|
|
|
|
|
|
- `EventEntry.fineTimeLeft` (days → "X hr, Y min left") for the bars label.
|
|
|
|
|
|
- Re-themed all home-screen widgets to slate bg + orange: Day Progress, Tasks Done
|
|
|
|
|
|
Today, Event Countdown (dots), My Tasks. Lock-screen accessory widgets stay on
|
|
|
|
|
|
`.thinMaterial` (system-tinted on the Lock Screen).
|
|
|
|
|
|
|
|
|
|
|
|
Files: `WidgetViews.swift`, `EventCountdownWidget.swift`, `MyTasksWidget.swift`,
|
|
|
|
|
|
`KisaniCalWidgets.swift`.
|
Workout check-in: missed state + rest-day compensation (KC-16)
- Notification actions on workout reminders/check-ins: "Yes, I completed
it", "No, I didn't" (marks the day missed, then asks to compensate on a
rest day), "Remind me in 1 hour" (snooze).
- VM: missedDates + compensations (persisted/synced), per-date
markWorkoutDone/Missed, workoutStatus, upcomingRestDays,
scheduleCompensation, promptCompensation, checkPendingMissed.
program(for:) returns a compensation program on its rest day.
- CompensationSheet: pick a rest day or keep as missed; compensation days
get a one-off "Missed workout recovery" reminder.
- Long-press menus: workout row (Done / Not Done / Compensate) in Today +
Calendar; exercise cards (Mark as Done / Not Done). All actions are
per-date — one occurrence never affects another.
- Workout row shows Pending / Done / Missed + "Compensation" label.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-06-10 23:06:58 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-16 — Workout check-in, missed state, and rest-day compensation
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified; notification actions need a real device)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Workout / Notifications
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
Workout reminders should ask "Have you done this workout?" with Yes / No / Snooze.
|
|
|
|
|
|
Saying No marks that day missed and offers to compensate on a rest day. Long-press
|
|
|
|
|
|
on workout/exercise cards gives quick Done / Not Done / Compensate actions. Each
|
|
|
|
|
|
scheduled day keeps its own completion state.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- **VM:** `missedDates` + `compensations` (persisted + iCloud), `workoutStatus(on:)`
|
|
|
|
|
|
(pending/done/missed), `markWorkoutDone/markWorkoutMissed(on:)` (per-date only),
|
|
|
|
|
|
`upcomingRestDays`, `scheduleCompensation`, `promptCompensation`,
|
|
|
|
|
|
`checkPendingMissed`. `program(for:)` honors compensations; a compensation day
|
|
|
|
|
|
is not a rest day.
|
|
|
|
|
|
- **Notifications:** WORKOUT_CONFIRM category now has "Yes, I completed it ✓",
|
|
|
|
|
|
"No, I didn't" (→ marks missed + asks compensation on next open), and "Remind me
|
|
|
|
|
|
in 1 hour" (snooze re-delivers). Daily reminder + check-in both use it.
|
|
|
|
|
|
Compensation days get their own one-off reminder ("Missed workout recovery").
|
|
|
|
|
|
- **UI:** `CompensationSheet` (rest-day picker, "No, keep as missed"); long-press
|
|
|
|
|
|
menus on the calendar/Today workout row (Done / Not Done / Compensate) and on
|
|
|
|
|
|
exercise cards (Mark as Done / Not Done); workout row subtitle shows
|
|
|
|
|
|
Pending / Done / Missed and a "Compensation ·" prefix (missed shows accent color).
|
|
|
|
|
|
- Daily per-date rules unchanged (KC-1/KC-10): completing Tuesday never completes
|
|
|
|
|
|
Saturday.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `ExerciseModels.swift`, `NotificationManager.swift`, `ContentView.swift`,
|
|
|
|
|
|
`WorkoutView.swift`, `CalendarView.swift`, `TodayView.swift`.
|
|
|
|
|
|
|
|
|
|
|
|
### How to test (device)
|
|
|
|
|
|
1. Enable workout reminder/check-in in Settings; when it fires, use the actions.
|
|
|
|
|
|
2. "No, I didn't" → open app → compensation sheet appears → pick a rest day →
|
|
|
|
|
|
that day now shows the program labeled Compensation (and gets a reminder).
|
|
|
|
|
|
3. Long-press the workout card in Today/Calendar → Done / Not Done / Compensate.
|
|
|
|
|
|
4. Long-press an exercise card in Workout → Mark as Done / Not Done.
|
2026-06-11 11:49:35 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-17 — Remove Event Countdown (dots) + Tasks Done Today widgets
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** Resolved (build-verified)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Widgets
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
The dot-grid "Event Countdown" and "Tasks Done Today" widgets were judged not up
|
|
|
|
|
|
to standard and removed entirely from the gallery.
|
|
|
|
|
|
|
|
|
|
|
|
### Removal
|
|
|
|
|
|
- `EventCountdownWidget` struct (kind `KisaniEventCountdown`) + `EventCountdownView`.
|
|
|
|
|
|
- `TasksCompleteWidget` (kind `KisaniTasksComplete`) + `TasksCompleteView` +
|
|
|
|
|
|
its only consumer `todayTaskCompletion()` in WidgetData.swift.
|
|
|
|
|
|
- Both deregistered from `KisaniWidgetBundle`.
|
|
|
|
|
|
- Kept (shared by the surviving bars widget): `EventConfigIntent`, `EventEntity`,
|
|
|
|
|
|
`EventQuery`, `EventProvider`, `EventEntry`, `CycleCountdownUnitIntent`,
|
|
|
|
|
|
`BarGrid`; `DotGrid` kept (used by Day Progress).
|
|
|
|
|
|
- Untouched: Event Countdown (Bars), My Tasks, Day Progress, Lock Screen rect +
|
|
|
|
|
|
circular, Task Live Activity.
|
|
|
|
|
|
|
|
|
|
|
|
Files modified: `KisaniCalWidgets.swift`, `EventCountdownWidget.swift`,
|
|
|
|
|
|
`WidgetViews.swift`, `WidgetData.swift`. No files deleted (shared code remains
|
|
|
|
|
|
in EventCountdownWidget.swift). No app-side settings referenced these widgets.
|
2026-06-11 18:16:30 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-18 — Bars widget: progress bar never fills; date pickers felt broken
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified, pending device build)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Widgets
|
|
|
|
|
|
|
|
|
|
|
|
### Symptoms
|
|
|
|
|
|
The Event Countdown (Bars) widget showed all bars dim regardless of time left,
|
|
|
|
|
|
and the Event date / Counting from rows in the config appeared not to work.
|
|
|
|
|
|
|
|
|
|
|
|
### Root causes
|
|
|
|
|
|
1. Auto (upcoming-queue) mode anchored progress to `Date()` on **every** refresh,
|
|
|
|
|
|
so elapsed time was always ~0 → empty bar forever.
|
|
|
|
|
|
2. Custom mode defaulted both `Event date` and `Counting from` to the same
|
|
|
|
|
|
instant (`Date.now` at config time) → zero-length span → progress 0. The raw
|
|
|
|
|
|
second-precision defaults also made the picker rows look broken.
|
|
|
|
|
|
3. The timeline only refreshed at midnight, so even a correct bar wouldn't move
|
|
|
|
|
|
during an "X hr left" countdown.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- Persistent per-event anchor (`kisani.widget.anchor.<id>` in the App Group):
|
|
|
|
|
|
progress fills from when an event was first tracked and resets naturally when
|
|
|
|
|
|
the tracked event changes. An explicit "Counting from" before the event wins.
|
|
|
|
|
|
- `targetDate`/`startDate` are now optional — rows read "Choose" until set, and a
|
|
|
|
|
|
missing custom date falls back to a 2-day stub window.
|
|
|
|
|
|
- Timeline pre-renders an entry every 30 minutes (12 h horizon) so the bar and
|
|
|
|
|
|
time-left label keep moving.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `KisaniCalWidgets/EventCountdownWidget.swift`.
|
|
|
|
|
|
Note: existing widget instances re-read their config; dates must be re-picked
|
|
|
|
|
|
once (params changed to optional).
|
2026-06-11 19:33:01 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-19 — Widgets: exact logo palette everywhere
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified, pending device build)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Widgets
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
All widgets should match the brand orange theme of the logo exactly.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- `WidgetTheme` now uses the precise brand palette: accent **RGB(232,98,42)**
|
|
|
|
|
|
(app `AppColors.accent`) on the logo's dark **RGB(26,29,34)** background —
|
|
|
|
|
|
previously a near-miss orange on a slate background.
|
|
|
|
|
|
- Every themed widget (Event Countdown Bars, My Tasks, Day Progress) inherits it.
|
|
|
|
|
|
- Task Live Activity: hardcoded accent → `WidgetTheme.accent`; background tint →
|
|
|
|
|
|
logo dark.
|
|
|
|
|
|
- Lock-screen ring tints → brand accent (renders in color on StandBy/home).
|
|
|
|
|
|
|
|
|
|
|
|
Files: `WidgetViews.swift`, `TaskLiveActivity.swift`.
|
2026-06-11 23:05:33 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-20 — "Track Countdown": zero-config bars widget driven from the app
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified, pending device build)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Widgets / Tasks
|
|
|
|
|
|
|
|
|
|
|
|
### Description
|
|
|
|
|
|
The bars widget should not need manual event entry: track any KisaniCal event
|
|
|
|
|
|
from the app and the widget displays it automatically (title, date, time left,
|
|
|
|
|
|
progress bars).
|
|
|
|
|
|
|
|
|
|
|
|
### Fix
|
|
|
|
|
|
- **App:** new `CountdownTracker` + a "Track Countdown" / "Stop Tracking
|
|
|
|
|
|
Countdown" item in the shared task long-press menu. Stores
|
|
|
|
|
|
`kisani.widget.trackedEvent` (+ `trackedSince`) in the App Group and reloads
|
|
|
|
|
|
widget timelines.
|
|
|
|
|
|
- **Widget:** the tracked event bypasses the widget configuration entirely.
|
|
|
|
|
|
- **Mode A** (one-off): progress = elapsed/(event − tracking date).
|
|
|
|
|
|
- **Mode B** (recurring birthdays/anniversaries): progress across the
|
|
|
|
|
|
occurrence span containing now (previous → next occurrence), derived from
|
|
|
|
|
|
the task's recurrence rule (`recurrenceSpan`).
|
|
|
|
|
|
- `WidgetTask` now decodes `isRecurring`/`recurrenceLabel` from the shared JSON.
|
|
|
|
|
|
- No tracked event → existing configuration (upcoming queue / picked / custom)
|
|
|
|
|
|
remains the fallback, exactly as before.
|
|
|
|
|
|
- Bar rendering already maps progress → filled (accent) vs remaining (dimmed)
|
|
|
|
|
|
bars; the screenshot showing static dim bars was the pre-KC-18 build.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `TaskContextMenu.swift`, `WidgetData.swift`, `EventCountdownWidget.swift`.
|
|
|
|
|
|
|
|
|
|
|
|
### How to test (device)
|
|
|
|
|
|
1. Long-press any task with a due date → "Track Countdown".
|
|
|
|
|
|
2. The bars widget switches to that event without touching its config.
|
|
|
|
|
|
3. A yearly birthday shows Mode B: bar spans last year's → this year's date.
|
|
|
|
|
|
4. Long-press the task again → "Stop Tracking Countdown" → widget falls back
|
|
|
|
|
|
to its configured mode.
|
2026-06-15 12:40:39 +03:00
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-21 — Eisenhower Matrix as a TickTick-style view (Priority × deadline)
|
|
|
|
|
|
|
Matrix/menus: Pick Date everywhere, time-based reminders, notification snooze (KC-21)
- Date menu now offers "Pick Date" (and Edit) in the Matrix grid cards and the
Calendar reschedule/move menu, matching the tasks view — both open the shared
TaskEditSheet via a new editingTask sheet.
- Reworked the reminder picker (TaskDatePickerSheet, shared by all entry points)
from day/week offsets to sensible time-based ones relative to the event time:
None, On time, 5 min, 30 min, 1 hour, 1 day, plus a Minutes/Hours/Days custom
wheel. Existing absolute reminderDates migrate to the nearest minute offset.
- Notifications gain Snooze actions (15/30/60/120 min) that reschedule the task
reminder; postpone now clears the Matrix urgency override.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 18:14:10 +03:00
|
|
|
|
**Status:** In Progress (implemented & build-verified, pending device QA)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Tasks / Matrix
|
|
|
|
|
|
|
2026-06-15 12:40:39 +03:00
|
|
|
|
### Problem
|
|
|
|
|
|
The Matrix treated importance as the task's *stored quadrant* — you placed a
|
|
|
|
|
|
task in a row and only a manual "Move" changed it. TickTick instead treats the
|
|
|
|
|
|
Matrix as a **view**: it auto-places every task from its **Priority** and **due
|
Matrix/menus: Pick Date everywhere, time-based reminders, notification snooze (KC-21)
- Date menu now offers "Pick Date" (and Edit) in the Matrix grid cards and the
Calendar reschedule/move menu, matching the tasks view — both open the shared
TaskEditSheet via a new editingTask sheet.
- Reworked the reminder picker (TaskDatePickerSheet, shared by all entry points)
from day/week offsets to sensible time-based ones relative to the event time:
None, On time, 5 min, 30 min, 1 hour, 1 day, plus a Minutes/Hours/Days custom
wheel. Existing absolute reminderDates migrate to the nearest minute offset.
- Notifications gain Snooze actions (15/30/60/120 min) that reschedule the task
reminder; postpone now clears the Matrix urgency override.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 18:14:10 +03:00
|
|
|
|
date**, while still allowing quick drag/menu moves.
|
2026-06-15 12:40:39 +03:00
|
|
|
|
|
|
|
|
|
|
### Fix (model — `TaskItem.swift`)
|
Matrix/menus: Pick Date everywhere, time-based reminders, notification snooze (KC-21)
- Date menu now offers "Pick Date" (and Edit) in the Matrix grid cards and the
Calendar reschedule/move menu, matching the tasks view — both open the shared
TaskEditSheet via a new editingTask sheet.
- Reworked the reminder picker (TaskDatePickerSheet, shared by all entry points)
from day/week offsets to sensible time-based ones relative to the event time:
None, On time, 5 min, 30 min, 1 hour, 1 day, plus a Minutes/Hours/Days custom
wheel. Existing absolute reminderDates migrate to the nearest minute offset.
- Notifications gain Snooze actions (15/30/60/120 min) that reschedule the task
reminder; postpone now clears the Matrix urgency override.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 18:14:10 +03:00
|
|
|
|
- Replaced whole-quadrant override with `urgencyOverride: Bool?`.
|
|
|
|
|
|
- `nil` = urgency is computed from due date.
|
|
|
|
|
|
- `true` = force urgent column.
|
|
|
|
|
|
- `false` = force not-urgent column.
|
2026-06-15 12:40:39 +03:00
|
|
|
|
- Importance is now `priority == .high` (top row), not the stored quadrant.
|
Matrix/menus: Pick Date everywhere, time-based reminders, notification snooze (KC-21)
- Date menu now offers "Pick Date" (and Edit) in the Matrix grid cards and the
Calendar reschedule/move menu, matching the tasks view — both open the shared
TaskEditSheet via a new editingTask sheet.
- Reworked the reminder picker (TaskDatePickerSheet, shared by all entry points)
from day/week offsets to sensible time-based ones relative to the event time:
None, On time, 5 min, 30 min, 1 hour, 1 day, plus a Minutes/Hours/Days custom
wheel. Existing absolute reminderDates migrate to the nearest minute offset.
- Notifications gain Snooze actions (15/30/60/120 min) that reschedule the task
reminder; postpone now clears the Matrix urgency override.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 18:14:10 +03:00
|
|
|
|
Medium/Low/None stay in the bottom row.
|
|
|
|
|
|
- Urgency is deadline-driven:
|
|
|
|
|
|
- default urgent window = 3 days
|
|
|
|
|
|
- birthday/domain/annual/renewal/subscription/exam/deadline = 14 days
|
2026-06-15 12:40:39 +03:00
|
|
|
|
Auto-placement: Q1 = High+urgent, Q2 = High+later, Q3 = not-High+urgent,
|
Matrix/menus: Pick Date everywhere, time-based reminders, notification snooze (KC-21)
- Date menu now offers "Pick Date" (and Edit) in the Matrix grid cards and the
Calendar reschedule/move menu, matching the tasks view — both open the shared
TaskEditSheet via a new editingTask sheet.
- Reworked the reminder picker (TaskDatePickerSheet, shared by all entry points)
from day/week offsets to sensible time-based ones relative to the event time:
None, On time, 5 min, 30 min, 1 hour, 1 day, plus a Minutes/Hours/Days custom
wheel. Existing absolute reminderDates migrate to the nearest minute offset.
- Notifications gain Snooze actions (15/30/60/120 min) that reschedule the task
reminder; postpone now clears the Matrix urgency override.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 18:14:10 +03:00
|
|
|
|
Q4 = the rest.
|
|
|
|
|
|
- `moveToQuadrant` updates real attributes:
|
|
|
|
|
|
- vertical movement sets Priority (top → High; moving down demotes High → Medium)
|
|
|
|
|
|
- horizontal movement sets `urgencyOverride` only if the target column disagrees
|
|
|
|
|
|
with date-derived urgency.
|
|
|
|
|
|
- Editing due date (`setDate`) or saving the editor (`updateTask`) clears
|
|
|
|
|
|
`urgencyOverride` so the task re-places live.
|
|
|
|
|
|
- Category changes, priority changes, and date changes refresh the legacy
|
|
|
|
|
|
`quadrant` color/widget fallback to match computed placement.
|
2026-06-15 12:40:39 +03:00
|
|
|
|
- `addTask` applies KisaniCal defaults when no priority is picked: birthday /
|
|
|
|
|
|
domain / annual (+ title keywords exam, subscription, renew, expir) → High;
|
|
|
|
|
|
workout / gym / exercise → Medium.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix (create UI — `TodayView.swift`)
|
|
|
|
|
|
- `AddTaskSheet` no longer has a manual **quadrant** selector. It now exposes a
|
|
|
|
|
|
**Priority** menu (flag icon). User picks Priority + Date only; placement is
|
|
|
|
|
|
computed. Adding from a Matrix quadrant seeds High for the top row.
|
Matrix/menus: Pick Date everywhere, time-based reminders, notification snooze (KC-21)
- Date menu now offers "Pick Date" (and Edit) in the Matrix grid cards and the
Calendar reschedule/move menu, matching the tasks view — both open the shared
TaskEditSheet via a new editingTask sheet.
- Reworked the reminder picker (TaskDatePickerSheet, shared by all entry points)
from day/week offsets to sensible time-based ones relative to the event time:
None, On time, 5 min, 30 min, 1 hour, 1 day, plus a Minutes/Hours/Days custom
wheel. Existing absolute reminderDates migrate to the nearest minute offset.
- Notifications gain Snooze actions (15/30/60/120 min) that reschedule the task
reminder; postpone now clears the Matrix urgency override.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 18:14:10 +03:00
|
|
|
|
- Fixed no-date creation: a task without an explicit parsed/picked date stays
|
|
|
|
|
|
"No Date" instead of silently becoming today/urgent.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix (Matrix UI — `MatrixView.swift`, `TaskContextMenu.swift`)
|
|
|
|
|
|
- Completed tasks are hidden from the 2×2 Matrix grid by default, but remain in
|
|
|
|
|
|
the per-quadrant detail Completed section.
|
|
|
|
|
|
- Rows with an urgency override show a small **Manual** badge.
|
|
|
|
|
|
- Context menu includes **Reset Matrix Urgency** when an urgency override exists.
|
|
|
|
|
|
- Move menu shows all four quadrants, with a checkmark on the current quadrant.
|
2026-06-15 12:40:39 +03:00
|
|
|
|
|
|
|
|
|
|
### How to test
|
|
|
|
|
|
1. New task, no priority, far date → lands in Q4; raise to High → jumps to Q2.
|
Matrix/menus: Pick Date everywhere, time-based reminders, notification snooze (KC-21)
- Date menu now offers "Pick Date" (and Edit) in the Matrix grid cards and the
Calendar reschedule/move menu, matching the tasks view — both open the shared
TaskEditSheet via a new editingTask sheet.
- Reworked the reminder picker (TaskDatePickerSheet, shared by all entry points)
from day/week offsets to sensible time-based ones relative to the event time:
None, On time, 5 min, 30 min, 1 hour, 1 day, plus a Minutes/Hours/Days custom
wheel. Existing absolute reminderDates migrate to the nearest minute offset.
- Notifications gain Snooze actions (15/30/60/120 min) that reschedule the task
reminder; postpone now clears the Matrix urgency override.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-15 18:14:10 +03:00
|
|
|
|
2. New task with no date → stays in right column until given a due date/reminder.
|
|
|
|
|
|
3. Drag Q2 → Q1 when due date is far out → Manual badge appears.
|
|
|
|
|
|
4. Reset Matrix Urgency → task returns to its date-derived column.
|
|
|
|
|
|
5. Drag Q1 → Q4 → High demotes to Medium and urgency is overridden if needed.
|
|
|
|
|
|
6. Open the task, change its due date → urgency override clears, re-places by rule.
|
|
|
|
|
|
7. Add a "Mum's birthday" with no priority → auto-High and uses 14-day urgency window.
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
## KC-22 — Quick postpone / snooze from task menus and lock screen
|
|
|
|
|
|
|
|
|
|
|
|
**Status:** In Progress (implemented & build-verified, pending device QA)
|
|
|
|
|
|
**Reported by:** User
|
|
|
|
|
|
**Area:** Tasks / Calendar / Matrix / Notifications
|
|
|
|
|
|
|
|
|
|
|
|
### Problem
|
|
|
|
|
|
Long-pressing a task/event in Today, Matrix, or Calendar required going into the
|
|
|
|
|
|
date editor or using only coarse "+1 day" actions. Lock-screen task reminders
|
|
|
|
|
|
also only supported "Mark Complete". The user wanted standard task-manager
|
|
|
|
|
|
snooze choices directly from the pressed item and notification actions.
|
|
|
|
|
|
|
|
|
|
|
|
### Fix (app task menus)
|
|
|
|
|
|
- Added a shared **Postpone** submenu to `TaskMenuItems`:
|
|
|
|
|
|
- 15 Minutes
|
|
|
|
|
|
- 30 Minutes
|
|
|
|
|
|
- 1 Hour
|
|
|
|
|
|
- 2 Hours
|
|
|
|
|
|
- Tomorrow
|
|
|
|
|
|
- Wired the submenu through:
|
|
|
|
|
|
- Today timeline + overdue/upcoming sections
|
|
|
|
|
|
- Matrix grid + quadrant detail sections
|
|
|
|
|
|
- Calendar day timeline
|
|
|
|
|
|
- `TaskViewModel.postpone(_:minutes:)` applies the nudge:
|
|
|
|
|
|
- existing reminder → reminder moves forward
|
|
|
|
|
|
- due date with no reminder → due date/time moves forward and becomes timed
|
|
|
|
|
|
- no date/reminder → creates a reminder
|
|
|
|
|
|
|
|
|
|
|
|
### Fix (lock screen notifications)
|
|
|
|
|
|
- Task reminder notifications now include actions:
|
|
|
|
|
|
- 15 min
|
|
|
|
|
|
- 30 min
|
|
|
|
|
|
- 1 hour
|
|
|
|
|
|
- 2 hours
|
|
|
|
|
|
- Notification response handler updates the stored task reminder and schedules
|
|
|
|
|
|
a one-off snoozed notification for the selected delay.
|
|
|
|
|
|
|
|
|
|
|
|
Files: `TaskContextMenu.swift`, `TaskItem.swift`, `TodayView.swift`,
|
|
|
|
|
|
`MatrixView.swift`, `CalendarView.swift`, `NotificationManager.swift`.
|
|
|
|
|
|
|
|
|
|
|
|
### How to test
|
|
|
|
|
|
1. Long-press a task in Today → Postpone → 15 Minutes; reminder/due time moves.
|
|
|
|
|
|
2. Repeat from Matrix grid, Matrix detail, and Calendar day timeline.
|
|
|
|
|
|
3. Open Move from the same menu → all four quadrants are visible, current one checked.
|
|
|
|
|
|
4. Trigger a task reminder notification on device → verify 15/30/60/120 minute
|
|
|
|
|
|
lock-screen actions appear.
|
|
|
|
|
|
5. Tap a lock-screen snooze action → task reminder updates and notification
|
|
|
|
|
|
re-delivers after the selected interval.
|