# BUG-002: Spaces-only title creates an empty-title task and shows success feedback

- Project: TaskFlow — independent guided QA and UX evaluation.
- Test / run: TC-002 / RUN-003.
- Requirements: REQ-01 and REQ-11.
- Environment: Release 1.0, Windows desktop, Chrome (version not recorded).
- Record date: October 14, 2026.
- Status: Verified for the tested invalid-title and valid-correction cases on prototype 1.3 (RUN-004 and RUN-005). Original failure remains documented on 1.0; broader regression is pending.

## Setup and reproduction

The guided procedure specified five spaces in Task title, blank Due date, Medium priority, and Unassigned. The learner reported creation of an untitled task without a rejection message. The screenshots show the resulting record; they do not capture the exact spaces entered before submission.

1. Select release 1.0 and Show status All.
2. Enter five spaces in Task title; leave Due date blank, Priority Medium, and Assignee Unassigned.
3. Click Create task.
4. Inspect the task list and form feedback.
5. Refresh and inspect whether the untitled task remains.

## Expected result

Reject the title after trimming spaces, show useful validation feedback, and create no record. The task count must remain unchanged. This is expected application behavior; the eventual test verdict is determined by comparing actual behavior with it.

## Actual result and evidence

The learner reports that an untitled task was created with no rejection message. The first screenshot shows:

- Release 1.0 and All filter.
- An `(empty title)` card, Open status, Medium priority, Unassigned, and No due date.
- A total of two tasks. A pre-submission count was not captured, so an exact before/after count increase is not independently established by these images.
- A green message: “Task created. Check All or Open if your current filter hides it.”

The second screenshot, identified by the learner as after refresh, shows the same untitled task and total count. The temporary success message is no longer displayed.

- [After creation, before refresh](../evidence/session-02/RUN-003_TC-002_v1.0_after-create.png)
- [After refresh](../evidence/session-02/RUN-003_TC-002_v1.0_after-refresh.png)

Blank due date and Unassigned are permitted by the lab requirements and setup. They are not separate failures in this test. The defect concerns the required title and the success feedback for an invalid submission.

## User impact and proposed triage

An untitled task does not tell the coordinator what work needs doing. Success feedback can encourage the user to continue without correcting the unusable entry. These are inferred workflow risks, not measured participant reactions.

- Proposed severity: Medium, using the lab rubric; an invalid record is created, but entering a valid title permits the intended workflow.
- Proposed priority: P1 under the proposed practice release criteria, which require title validation to pass.
- Reproducibility: One submission reported; screenshots document the resulting record before and after refresh, not a second independent submission.
- Correction flow: Entering a meaningful title was tested successfully on prototype 1.3 (RUN-005). This does not establish a workaround tested against the original 1.0 failure.

## QA and UX follow-up

Verify that invalid submission creates no record. Evaluate an error state that places actionable text near Task title, such as “Enter a task title. Spaces alone aren't accepted.” Keep existing inputs available for correction and make the feedback discoverable with a keyboard.

The recommendation is a design proposal. Implemented behavior and user comprehension still need evaluation.

## Prototype retest: RUN-004, release 1.3

On October 14, 2026, the learner repeated the guided invalid-title check in Chrome and reported no task was created and the error appeared beneath Create task. The [supplied screenshot](../evidence/session-03/RUN-004_TC-UX-001_v1.3_title-error.png) confirms release 1.3, zero tasks, and the expected message. The invalid-input check is **Pass** for this release and input.

The user-selected feedback placement was implemented by the assistant. This retest does not change the recorded failure on release 1.0.

## Correction-flow check: RUN-005, release 1.3

The learner replaced the invalid title with `Workshop 1 setup` and reported successful creation. The [supplied screenshot](../evidence/session-03/RUN-005_TC-UX-002_v1.3_successful-recovery.png) shows exactly one task with the expected title, Open status, Medium priority, Unassigned, and no date. The previous screenshot showed zero tasks. The title error is absent and green success feedback is visible. Result: **Pass** for this correction-flow case.

Broader input regression, saved-data persistence, accessibility, and participant understanding remain outside these two completed checks.