Boards
Learn how to create and manage ticket boards for organizing customer feedback, bug reports, and feature requests.
Overview
Boards serve as containers for organizing tickets into different categories based on their purpose. Each board can have multiple forms for collecting different types of feedback.
Board Types
Choose from three board types when creating a new board:
BugUsed for collecting and tracking software bugs and technical issues.
Feature RequestDesigned for gathering feature suggestions and enhancement requests. These boards support public sharing.
CustomFlexible boards for any other type of ticket management needs.
Creating Boards
- Navigate to Settings → Boards
- Click "New Board" button
- Configure the board:
- Name: Descriptive title for the board
- Type: Select the appropriate board type
- The system automatically creates a default column for new boards
Managing Boards
Board List
The boards overview displays:
- Board name (clickable link to open the board)
- Type badge indicating the board category
- Associated forms showing available submission forms
- Actions for board management
Board Actions
Access board management through the actions column:
Settings
Navigate to individual board settings to modify name and type.
Delete Board
Remove boards that are no longer needed. Note that:
- Default boards cannot be deleted
- Deleting a board removes all associated tickets, forms, and columns
- This action cannot be undone
Managing Forms
Each board can have multiple forms for different submission scenarios:
Viewing Forms
Forms appear as buttons in the "Form" column, allowing quick navigation to form settings.
Adding Forms
Click "Add Form" on any board to create a new submission form. This opens the form builder where you can:
- Configure form fields
- Set up automated responses
- Customize collection settings
Board Filtering
Use the built-in filters to quickly find specific boards:
- Name: Search by board title
- Type: Filter by Bug, Feature Request, or Custom boards
Boards are sorted alphabetically by name by default.
Best Practices
Organization
- Create separate boards for different product areas or teams
- Use consistent naming conventions
- Choose the appropriate board type for your use case
Maintenance
- Regularly review and archive completed boards
- Keep form names descriptive and user-friendly
- Monitor board usage to identify consolidation opportunities
Security
- Feature Request boards can be made public
- Bug and Custom boards remain private by default
- Control access through organization permissions