# BUG-001: Task due date is lost after refreshing the page

- Project: TaskFlow — independent manual QA practice.
- Status: Original failure reported by learner; date preservation verified with a controlled fixture on release 1.3 in RUN-006, with before/after screenshots. Original failure evidence remains limited to the learner report and later screenshots showing the date absent.
- Linked requirement: REQ-03 — the selected due date must remain after refresh.
- Linked test / execution: TC-005 / RUN-002.
- Record date: October 14, 2026. Exact execution time not recorded.
- Environment: Windows desktop using Google Chrome, confirmed by the learner. Chrome version and selected release not yet confirmed. Release 1.0 was requested in the exercise instructions; the learner has not explicitly confirmed the selector value.

## Learner's observed behavior

The learner reported entering a title, due date, priority, and assignee, creating the task, and refreshing. The task remained, and its title, priority, and assignee remained unchanged. Its due date instead indicated there was no date, although November 15 had been selected.

## Reproduction steps from the reported run

1. Enter a task title, a November 15 due date, a priority, and an assignee.
2. Click Create task.
3. Refresh the browser page.
4. Inspect the saved task's fields.

Exact title, priority, assignee, and selected date year were not explicitly provided in the learner's report. The exercise suggested Prepare welcome packs, November 15, 2026, High, and Mia Chen; those suggestions are not recorded here as confirmed inputs. A before-refresh observation or screenshot has not yet been provided.

## Expected result

The saved task retains the selected November 15 due date after refresh, alongside the other entered values, as required by REQ-03.

## Actual result

After refresh, the task remains with unchanged title, priority, and assignee, but its due date indicates no date was selected.

## Impact and proposed triage

The coordinator loses a recorded deadline and may miss scheduled preparation work. Proposed severity: High under the lab's saved-business-information-loss rubric. Proposed priority: P1 because the lab's release criteria require no unresolved loss of saved dates. These are practice recommendations, not real business decisions.

## Evidence and follow-up

- Original evidence source: learner's report in this chat. Later RUN-003 screenshots show the earlier task without a date, but not its original date entry.
- Original-failure reproducibility: one failure reported; no second independent reproduction of that failure is recorded.
- Workaround: none tested.
- Linked verification: RUN-006 on release 1.3, Pass for the controlled fixture below. Broader date coverage remains pending.

## Release 1.3 verification: RUN-006

The learner created `prepare speaker badges` with due date `2026-11-15`, priority High, and assignee Mia Chen. They supplied [before-refresh](../evidence/session-03/RUN-006_TC-005_v1.3_before-refresh.png) and [after-refresh](../evidence/session-03/RUN-006_TC-005_v1.3_after-refresh.png) screenshots and confirmed the refresh action.

Both images show the same title, date, priority, and assignee, with Open status. The total remains two, and the earlier Workshop 1 setup task remains. Result: **Pass** for the specified persistence check on release 1.3, Chrome on Windows desktop, October 14, 2026.

The original run's exact data and release were not fully captured, so this verifies the same reported failure mode with explicit new inputs rather than claiming an identical replay. It does not establish every date scenario, browser, or release has passed.

This record documents the learner's manual observation; author verification results are not counted as learner execution evidence.