Fesk
  • Features
  • Pricing
  • FAQ
  • Documentation
  • Get Started Free
  • Sign In
  • Go to App

Getting Started

  • Quick Start
  • Creating Tickets
  • Getting Around
  • Keyboard Shortcuts

Account & Security

  • Account & Security
  • Single Sign-On (SSO)

User Guide

  • The Board
  • List View
  • Working with Tickets
  • Rich-Text Editor
  • Resolution Types
  • Ticket Templates
  • Canned Responses
  • Time Tracking
  • AI Features
  • Ticket Translation
  • Customer Portal
  • Profiles & Account Switching
  • Knowledge Base
  • Saved Views
  • Dashboards
  • Activity Feed
  • Search
  • Notifications
  • Push Notifications
  • Install & Offline Use
  • Collision Detection
  • Reports
  • Team Workload
  • Ticket Linking
  • Bulk Operations
  • Ticket Merging

Admin Guide

  • Workspace Setup
  • User Management
  • Ticket Types & Custom Fields
  • Workflow Statuses
  • Email Integration
  • Email Notification Templates
  • Public Contact Form
  • Automation
  • AI Ticket Workflows
  • Recurring Tickets
  • Import / Export
  • SLA Policies
  • Customer Satisfaction
  • Webhooks
  • Connectors
  • AI Configuration
  • Audit Logs
  • Data & Privacy
  • Billing & Subscription
  • Workspaces

API & Developers

  • API Overview
  • Interactive API Reference

Workflow Statuses

Workflow statuses are the columns tickets move through on the board. You can rename, add, and reorder them for each workspace.

The default flow

Out of the box every workspace has four statuses, shown as lanes on the board:

  • Open: new, not started
  • Work in Progress: actively being worked
  • Waiting: blocked, usually on the customer or a third party
  • Closed: done

Customizing statuses

Go to Settings → Workflow Statuses. From there you can:

  • Add a status (e.g. "In Review", "Approved"), it becomes a new board column
  • Rename an existing status
  • Reorder statuses to set the left-to-right flow on the board
  • Mark which statuses count as open vs resolved/closed for reporting and SLA purposes

Statuses are per workspace, so different teams can run different flows. See workspaces for how that isolation works.

Transitions

Beyond the list of statuses, you can define transitions: which moves between statuses are allowed, and what happens on the way. Under Settings → Transitions you control the path tickets take (for example, requiring a ticket to pass through "In Review" before "Closed"), and which statuses prompt for a resolution type when a ticket is closed.

Related

  • See statuses in action as lanes in the board.
  • Status values are mappable when you import tickets, unmatched values are rejected with a suggestion.
Fesk

A shared ticket board for support teams.

Product

  • Features
  • Pricing
  • Documentation
  • Status

Company

  • Contact

Resources

  • Help Center
  • FAQ
  • API Docs

Legal

  • Privacy Policy
  • Terms of Service
  • Security
  • GDPR
  • Data Processing Agreement
  • Legal Notice

© 2026 Fesk. All rights reserved.