Tickets
Track work items with types, priorities, assignments, comments, file attachments, and more.
Tickets are the building blocks of your projects in Spedy. Every piece of work -- whether it's a bug to fix, a feature to build, or a task to complete -- lives as a ticket on a board. Each ticket gets a unique, human-readable ID based on the board prefix, like CS-42 or ACME-17, so you can easily reference it in conversations.
Ticket Types
Every ticket has a type that describes the kind of work it represents:
| Type | When to use it |
|---|---|
| Bug | Something is broken or behaving unexpectedly |
| Feature | A new capability or improvement to build |
| Epic | A large piece of work that spans multiple tickets |
These are the three built-in ticket types. You can also create custom ticket types for your organization to match your team's workflow -- for example, "Task", "Chore", or "Improvement". Custom types are managed in your organization settings and can be made available on any board.
Priorities
Set a priority on each ticket to help your team know what to focus on first:
| Priority | What it means |
|---|---|
| Critical | Needs immediate attention -- something is severely broken or blocking |
| High | Important -- should be addressed soon |
| Medium | Standard priority (this is the default) |
| Low | Can wait -- address when time allows |
Working with the Status Workflow
Tickets move through your board's columns as work progresses. You can drag a ticket between columns to update its status, or change the status directly from the ticket detail view. Spedy groups statuses into Planning, Blocked, Active, and Final categories so you always have a clear picture of where things stand.
Assigning Tickets
Assign a ticket to a team member to make it clear who's responsible. The assignee will receive a notification and can see all their assigned tickets in one place. You can reassign tickets at any time as priorities shift.
Comments
Use comments to discuss a ticket with your team. You can mention other users with @name to notify them directly. Comments support rich text formatting, so you can include links, code snippets, and more. Comments can be marked as secret (internal-only) using the isSecret flag, making them visible only to your team and hidden from external customer users.
File Attachments
Attach files to any ticket -- screenshots, documents, designs, or anything else your team needs. Files are securely stored and can be downloaded by anyone who has access to the board.
You can also import Spedy Selection Packages (.spsx) when creating a ticket to pre-fill the form with structured selections, screenshots, and comments. See SPSX Import for details.
Labels
Labels let you tag tickets with custom categories that make sense for your project. Create labels like "Frontend", "Urgent", or "Design Review" at the board level, and apply as many as you need to each ticket. Labels make it easy to filter and find related tickets.
Linking Tickets
Connect related tickets to show how work items depend on each other:
| Link type | What it means |
|---|---|
| Blocks | This ticket must be completed before another can proceed |
| Is blocked by | This ticket cannot proceed until another is completed |
| Relates to | These tickets are related but don't block each other |
| Duplicates | This ticket is a duplicate of another one |
There are four link types in total. When you create a "Blocks" link, the inverse "Is blocked by" link is automatically created on the other ticket.
Due Dates
Set a due date on any ticket to track deadlines. Tickets with upcoming due dates are highlighted in the dashboard and pulse view so you can stay ahead of deadlines. Due dates can be set and changed from the ticket detail view.
The Ticket Detail View
Click on any ticket to open its full detail view. From here you can see and edit everything: the title and description, type, priority, status, assignee, due date, labels, linked tickets, comments, and attachments. You'll also find a complete activity history showing every change made to the ticket.
Subtasks
Break large tickets down into smaller, manageable pieces using subtasks. Any ticket can have child tickets that track individual steps of the work. Subtasks appear directly in the parent ticket's detail view, and each subtask has its own status, assignee, and priority. If you complete or move the parent ticket while subtasks are still open, Spedy will warn you so nothing gets lost.
Epics and Stories
Epics group related tickets that all belong to the same larger initiative. Unlike subtasks, stories under an Epic are still first-class tickets -- they keep their own status, assignee, and priority, and can move across your board independently, while the Epic shows the bigger picture.
Attaching a ticket to an Epic
Any ticket can be attached to an Epic on the same board:
- Open the ticket you want to group.
- In the ticket properties, open the Epic field.
- Search by title or ticket ID and pick the Epic.
You can reassign a ticket to a different Epic or clear the field to remove it from any Epic. Only tickets of type Epic on the same board can be selected -- a ticket cannot be its own Epic.
Managing stories from the Epic
When you open an Epic, a Tickets in this Epic panel lists every story attached to it. From there you can:
- Jump to any story with one click
- Add more tickets to the Epic via the Add ticket search
- Remove a ticket from the Epic without deleting it
Filtering by Epic
In the Issues Hub and on board pages, you can filter the list to show only tickets belonging to one or several Epics. This is useful to quickly review the progress of a large initiative across boards.
Watching Tickets
Want to stay in the loop on a ticket without being the assignee? Watch it. You'll automatically receive notifications whenever there's activity. Ticket creators and anyone who comments are added as watchers by default.
Time Tracking on Tickets
If time tracking is enabled for your workspace, you can log time directly on any ticket. Start a timer while you work and stop it when you're done, or add manual time entries after the fact. Time logged on a ticket is visible in the ticket detail view and contributes to board-level time reports. See Time Tracking for more details.