Boards

The Boards settings page provides centralized management for your ticket organization system, allowing you to create and maintain different boards that categorize and organize customer feedback and support tickets.

Overview

The boards settings page serves as the administrative hub for managing your ticket management infrastructure. Here you can create new boards, configure board types, manage associated forms, and organize how different types of customer interactions are categorized and processed.

Boards are the foundation of your ticket management system. They determine how tickets are organized, what forms are available for submission, and how your team processes different types of customer feedback.

Page Layout

The boards settings page displays a comprehensive table view of all boards in your organization, with the following key information:

  • Board Name: Clickable links that navigate directly to the board's ticket view
  • Type: Badge indicating the board category (Bug, Feature Request, or Custom)
  • Forms: Interactive buttons showing available submission forms for each board
  • Actions: Settings and delete options for board management

Key Features

Board Management

  • Create New Boards: Add new boards with predefined types and automatic column setup
  • Board Navigation: Direct links to view tickets within each board
  • Board Settings: Access individual board configuration options
  • Board Deletion: Remove boards with cascade deletion of associated tickets and forms

Form Association

  • View Forms: See all forms linked to each board as clickable buttons
  • Add Forms: Create new submission forms directly from the boards table
  • Form Navigation: Quick access to form builder and configuration

Organization Tools

  • Filtering: Search boards by name or filter by type (Bug, Feature Request, Custom)
  • Sorting: Boards are displayed alphabetically by name by default

Connection to Tickets

Boards are directly connected to your ticket management system in several important ways:

Each board serves as a container that organizes tickets into logical categories, making it easier for your team to manage different types of customer interactions.

Ticket Organization

  • Board Types: Different board types (Bug, Feature Request, Custom) determine how tickets are categorized and processed
  • Column Structure: Each board contains columns that represent different stages of ticket processing (e.g., "New", "In Progress", "Resolved")
  • Ticket Storage: All tickets submitted through board forms are stored within their respective boards

Form Integration

  • Submission Pipeline: Forms attached to boards collect structured data that becomes ticket content
  • Automated Processing: Board forms can include welcome messages, custom fields, and thank you responses
  • Data Collection: Forms capture screenshots, recordings, email addresses, and other metadata for comprehensive ticket creation

Workflow Management

  • Ticket Views: The board interface provides kanban-style ticket management with drag-and-drop functionality
  • Assignment: Tickets can be assigned to team members within board views
  • Status Tracking: Board columns enable visual tracking of ticket progress through different stages

Practical Usage

Setting Up New Projects

  1. Create a new board in the appropriate type (Bug, Feature Request, or Custom)
  2. Add forms to collect specific information needed for that project type
  3. Configure board columns to match your team's workflow stages
  4. Share the board with relevant team members

Managing Multiple Products

  • Use separate boards for different products or services
  • Create feature request boards that can be made public for customer feedback
  • Maintain bug report boards for technical issue tracking

Form Strategy

  • Attach multiple forms to a single board for different submission scenarios
  • Use forms to collect different types of information (bug reports, feature requests, general feedback)
  • Configure forms with appropriate fields, validation, and automated responses

Best Practices

Board deletion is permanent and removes all associated tickets, forms, and data. Default boards cannot be deleted to ensure system stability.
  • Consistent Naming: Use clear, descriptive board names that indicate their purpose
  • Appropriate Types: Choose the right board type based on the primary use case
  • Form Organization: Keep forms focused and avoid creating too many forms per board
  • Regular Maintenance: Periodically review and archive completed boards
  • Access Control: Configure board permissions appropriately for your team's needs

For detailed information about board creation, management, and configuration options, see our comprehensive Boards documentation.