Turn project intent into governed, visible work.

Open the project Work space

If no board exists, Work shows an empty state with a route to create the first board. Loading, paginated results, move failures, and permission errors remain visible rather than presenting stale success.

Create the first board

1. Name the board.Use a stable delivery view such as Product delivery or Maintenance.
2. Create it.Mozaic creates the initial saved-query board with New, In progress, and Done columns.
3. Return to Work.The board displays matching work cards by lane. Empty columns remain visible.
4. Move accessibly.Drag a card between lanes or use its lane selector. Both perform the same version-checked transition.

Configure workflow lanes

1. Open the default board workflow.If the page says to create a default board first, complete the board workflow above.
2. Name each lane.Use language the team recognizes while retaining a canonical Open, In progress, or Done status.
3. Mark active work.Active-work lanes determine which assignments receive delivery attention.
4. Choose the default.New work begins in this lane.
5. Reorder, archive, or restore.Archived lanes stop being new transition targets without erasing historical transitions.
6. Save.The updated board version becomes the transition contract for subsequent moves.

A stale save can be rejected when another manager changed the board. Reload and reconcile the latest lane order instead of overwriting it.

Define work item types

Starter kinds are Task, Bug, Feature, and Private security report. Type definitions determine the label and optional typed custom fields available on items.

1. Select a definition.Review its active status and current immutable version.
2. Edit the display name and active state.Inactive types remain meaningful for existing items but cannot be chosen for new work.
3. Define fields.Use valid typed-field JSON for boolean, single select, multi-select, user, integer, date, or text fields, including choices and required state where applicable.
4. Create the new version.The server validates the definition. Existing items retain the type version under which their data was recorded.

Create a work item

1. Choose the type.Select Task, Bug, Feature, or Private security report. Project settings can version the labels and fields for the starter types but do not add another creation kind.
2. Write the title.Make the desired outcome easy to recognize on a board card.
3. Add the rich description.Include context, acceptance notes, tables, tasks, code, resource references, or ready media as appropriate.
4. Create.The item receives the workflow's default lane and opens its detail view.

Plan and execute from item detail

1. Refine the description.Edit rich prose; use Description history to inspect immutable earlier revisions.
2. Set ownership.Choose a team, one or more eligible assignees, labels, and an optional milestone.
3. Complete custom fields.Fill every field required by the exact type version. User choices are authorization-filtered.
4. Transition the work.Use Start progress, Resolve, Reopen, or another available lane transition. Transition history records actor and state change.
5. Discuss.Add flat rich comments, edit your own contribution, and inspect its revision history. Work comments do not have a conversation-resolution control.
6. Attach evidence.Select a file. The client binds the request to its SHA-256 digest; the attachment enters quarantine and is downloadable only after safe processing.

Relate work without duplicating it

From item detail, add a relation using the exact UUID of another visible work item.

Relates to

A symmetric contextual connection without dependency semantics.

Blocks

Records that this item prevents progress on the related item.

Duplicate of

Points this item to the authoritative existing item.

Relations are version-checked and may target only work visible to the current member. A not-found response can therefore mean the identifier is wrong or the target is outside your authorization.

Group work into a milestone

1. Enter title and due date.The date drives upcoming delivery attention on organization Home.
2. Add a rich description.Explain the outcome, scope, and release criteria.
3. Create and assign.Open each work item and select the milestone in its assignment fields.
4. Revise deliberately.Milestone description edits retain their revision history.

Handle abusive or sensitive submissions

Authorized moderators can mark the work item itself as visible, hidden, or spam with an audited reason. Individual work comments use the submitted-prose controls: hide and restore are reversible, while permanent security/legal redaction removes the comment's current and historical prose. Hard redaction requires fresh authentication where enforced and exact HARD REDACT confirmation and cannot be undone.

Common failures and current limits

• The canonical board lives under a project, not at organization Work.
• Type-definition changes create versions; they do not rewrite historical item data.
• Archived lanes and inactive types remain in history.
• Public work submission still requires authentication; security-report content stays private.