Tickets Overview
Track the work behind what customers ask for. Board, List and Scheduled views, filters, team assignees and recurring tickets.
Tickets are how your team tracks discrete units of work inside FutureBase: bugs customers hit, features they ask for, internal tasks, and recurring chores. Create them by hand, from a roadmap item, or automatically on a schedule.
Ticket statuses
| Status | Meaning |
|---|---|
| Backlog | Created but not yet prioritized |
| To do | Prioritized and ready to be worked on |
| In progress | Actively being worked on |
| In review | Work complete, awaiting review or verification |
| Blocked | Waiting on something outside the team's control |
| Done | Resolved |
| Cancelled | Not going ahead |
Move tickets between statuses by dragging them on the Board, or with the status dropdown on the ticket's page.
Ticket types
| Type | Use case |
|---|---|
| Task | Generic work item, anything that doesn't fit the other types |
| Feature | New functionality to build |
| Bug | Something that's broken and needs to be fixed |
| Improvement | Enhancement to existing functionality |
| Spike | Research or an investigation before the real work |
| Chore | Maintenance and upkeep |
Priorities
| Priority | When to use |
|---|---|
| Low | Nice to have, no urgency |
| Medium | Should be addressed in the current or next cycle |
| High | Blocks customers or has significant impact |
| Urgent | Customer-facing problem that needs attention now |
| Critical | Production outage |
Creating a ticket
Go to Tickets in the sidebar.
Click New ticket, or the + at the top of a Board column to start the ticket in that column.
Set the title, type and priority.
Optionally add a description, assign a team member, set a due date and an estimate, or tick Repeat on a schedule to make it a recurring ticket.
Click Create ticket.
Creating from a roadmap item
On the roadmap, open an item's menu (or its edit sheet) and choose Create ticket. The ticket is linked to the item, so the work behind what customers asked for is tracked to the end.
Ticket fields
| Field | Description |
|---|---|
| Title | Short description of the work (required) |
| Description | Detail, steps to reproduce, acceptance criteria. Markdown is supported |
| Type | Task, feature, bug, improvement, spike, chore |
| Status | Backlog, To do, In progress, In review, Blocked, Done, Cancelled |
| Priority | Low, medium, high, urgent, critical |
| Assignee | A member of your team, or unassigned |
| Due date | Optional deadline; overdue tickets are highlighted |
| Estimate | Optional, in hours |
| Roadmap items | The roadmap items this ticket implements, fixes or relates to |
Every field can be changed from the ticket's page, which also holds the team's comments. Tickets synced with Linear show the Linear issue, when it last synced, and a link to open it in Linear.
Views
Board: a column for every status. Drag tickets between columns to change their status, or within a column to reorder them. Cancelled tickets are folded into a list below the board, where you can reopen them.
List: a table of every ticket with sortable columns (title, status, type, priority, assignee, due date, last update).
Scheduled: your recurring tickets, with their next run, Pause/Resume and Edit.
The Board and List share the same filters at the top: search, assignee (a team member, or unassigned), type and priority. Filters are kept in the page's URL, so a filtered view can be bookmarked or shared with your team.
Next steps
Public Board
Share your roadmap and changelog with customers on a branded public page. Let them send feedback, vote on what's planned and follow your progress.
Recurring Tickets
Set up scheduled tickets that are created automatically, every day, week, month, year or on a cron schedule, for reviews, recurring tasks and operational chores.