Skip to content

Submissions

Submissions at /workspace/submissions (breadcrumb Workspace > Submissions) is the inbound issues queue: what the tenant reported about the product itself, waiting to become work. Nothing should sit here — every submission becomes a row somewhere real or gets closed with a reason.

  • The Issues rail carries search, status filter chips, and a list of issue rows with ages. Each row carries a status chip such as Assigned or Analyzing.
  • Intake here is bug-shaped — the queue is the tenant filing against its own system.
  • The detail pane starts empty (“Select an issue — Choose an issue from the sidebar to view its details and collaborate”). Picking a row swaps the empty state for the record; collaboration happens on the record, not in the rail.
Submissions at /workspace/submissions: issues rail with status filter chips above an empty detail pane reading Select an issue
  • Triage oldest-first when the queue is short, most-urgent-first when it is not. Requester and age break ties faster than gut feel — rows past 100 days are either fixed or forgotten, and the queue should say which.
  • A submission that becomes work belongs on the list that owns that kind of work: tasks under Tasks, project-shaped intake under Projects. Intake routes; it does not hold.
  • Intake that needs a person routes through Inbox: the attention queue carries the notice, the submission carries the facts.
  • Tasks: where intake becomes assigned work.
  • Projects: where project-shaped intake lands.
  • Inbox: the attention queue when intake needs someone.
  • Approvals: the queue when intake needs a decision.