Skip to content

Todos Document Flow

Operational tasks use a three-state lifecycle. There is no ETA Decline Rejection / Decline Cancellation.

Hub: Target Document Flow. Overview: Todos.

  • Pending
  • InProgress
  • Completed

#Statuses

Pending, InProgress, Completed

Priority: Low, Normal, High, Critical

Todo item lifecycle — Pending, InProgress, Completed

flowchart TB
  Start((Create)) --> Pending[Pending]
  Pending -->|Start| InProgress[InProgress]
  InProgress -->|Complete| Completed[Completed]
  Pending -->|Complete| Completed
  InProgress -->|Reopen| Pending
  Completed -->|Reopen| InProgress

  class Start egkStart
  class Pending egkDraft
  class InProgress egkActive
  class Completed egkSuccess
Actions

Board/list UI moves tasks between statuses (status change / drag). A formal Approve/Reject MudMenu is not part of the todo model.

Control Effect
Start / move to InProgress InProgress
Complete Completed
Reopen Back to Pending or InProgress

#Post-action sync

Kanban columns and list rows refresh after status change so chips and column membership match TodoStatus.

#Scenarios

Scenario Result
Complete pending task Completed
Reopen completed Leaves Completed
Expect Submit for approval Not part of Todos

Reconnecting to the server…

Please wait, or reload the page.