Zupright Documentation

Product documentation

Practical product guidance for Zupright modules. These public docs share content with in-app contextual help.

Browse documentation
Workflow Boards/ Start hereReady

Workflow Boards Overview

Understand how Workflow Boards help teams plan, track, and complete work.

Workflow Boards help a team manage work from request to completion. You can create projects, boards, tasks, backlogs, sprints, and workflow rules in one place.

Use this guide if you are setting up Workflow Boards for the first time or explaining the module to a new team member.

Key terms

Workspace
The top-level work area. Projects, boards, task types, statuses, and workflows are managed inside a workspace.
Project
A business project or product area that owns boards, tasks, and areas.
Board
A visual view of tasks. Boards usually show columns such as Backlogs, To Do, In Progress, and Done.
Task
A work item that needs planning, ownership, progress tracking, or completion.
Workflow
The set of allowed statuses and movements for a task.
Backlog
A list of work that is not yet planned for active delivery.
Sprint
A fixed planning period used by scrum teams to deliver a selected set of tasks.

What You Can Do

  • Create project boards for teams and delivery streams.
  • Create tasks with task type, priority, area, assignee, tags, description, and due date.
  • Move tasks across statuses using workflow rules.
  • Use a backlog to hold future work.
  • Plan sprints and complete active sprint work.
  • Connect parent and child tasks when work needs hierarchy.

Simple Setup

For most teams, start with one workspace, one project, one scrum or kanban board, a small set of statuses, and only the task types that the team really uses.

Who Uses It

Product owners, project managers, delivery leads, developers, QA users, operations teams, and business teams can use Workflow Boards to see what is planned, active, blocked, or done.

Best practices

  • Keep the first setup small. Add more task types or statuses only when the team needs them.
  • Use the backlog for work that is not ready for active execution.
  • Keep one clear owner on each task and add additional assignees only when collaboration is needed.
  • Review workflow transitions before teams start using a board in daily work.

Common mistakes

  • Creating too many board templates, statuses, or task types before the team has a real need.
  • Using Done for work that is actually cancelled or no longer required.
  • Moving tasks outside the agreed workflow and then losing reporting clarity.

Related documents