Informational Fresh jira_story: GOV-131

Lesson 2 of 7 — Task board and My Tasks

Governance Workspace Core · Source: Jira Story GOV-131 (8 pts) · Authority: Informational (the Jira story is authoritative).

Purpose

Give each owner a personal, auditable task board.

Why it matters

People act on what's clearly theirs; scoping plus audit make ownership real.

Where this lives

Runs in the Customer AI Governance platform (components: workspace). A scoped task query plus drag-to-change-status writes an audit row per transition. Learn teaches this read-only.

Workflow

Given a user's assigned tasks
When they open My Tasks
Then only their tasks show, sorted by due date, and drag changes status with an audit entry

Worked example

A member opens My Tasks and sees another team's tasks. What's wrong?

Scoping failed — My Tasks must show only the current user's tasks.

Acceptance criteria (authoritative — GOV-131)

Given a user's assigned tasks, when they open My Tasks, then only their tasks show, sorted by due date, and drag changes status with an audit entry.

Common pitfalls

Showing all tenant tasks instead of scoping to the current user.

Knowledge check

Scenario: A member opens My Tasks and sees another team's tasks. What's wrong?
Look for: Scoping failed — My Tasks must show only the current user's tasks.

Key concepts

My Tasks scoping
status transitions
audit on change

For the AI Tutor

Summary: Give each owner a personal, auditable task board.
When to use: teaching or answering questions about "task board and my tasks".
When NOT to use: validating or closing a task (that is GOV-133).
Key concepts: My Tasks scoping, status transitions, audit on change.

Completion criteria

Learner passes the scenario knowledge check and can point to the system state that satisfies GOV-131's acceptance criterion.

Module: LEARN-MOD-003 (Governance Workspace Core)
Provenance: LEARN-MAP-001 · Generation standard: LEARN-STD-002
Next: LEARN-LSN-017