One project per client. Tickets you can find again.
Every client project gets its own board with its own prefix and running numbers (NORD-214). On it: Kanban or list, a backlog with an approval step, epics, subtickets, links and fields you define yourselves.
- NORD-221 Role matrix for client accessTo do
- NORD-216 Rework onboarding flowIn progress
- NORD-214 Cache the product listIn progress
- NORD-209 Import fails on umlautsBlocked
- NORD-205 Footer linksDone
Projects, folders, prefixes.
A board is a project: one per client, grouped into folders, with its own short code, icon or logo. Finished projects are archived rather than deleted.
- Readable ticket IDs
- Every project has its own prefix and its own counter. Subtickets get a dotted number (NORD-214.2).
- Roles per project
- Members get the role admin, member or viewer per board; teams can be added as a whole.
- Retainer clients6 projects
- Fixed-price projects3 projects
- Internal2 projects
- Archived14 projects
From backlog to done, with fixed rules.
New tickets land in the backlog and only reach the board once approved. You add your own statuses inside fixed categories and show or hide them per project.
- Backlog with approval
- From the backlog a ticket can only move to To do. If you do not want the approval step, switch the backlog off per organization or project.
- Kanban and list
- Two views per board, remembered per project. Plus a cross-project ticket list and a global board.
- BacklogPlanning
- To doActive
- In progressActive
- BlockedBlocked
- DoneFinal
Bulk actions, filters, search.
In the ticket list and the backlog you change up to 500 tickets per action in one step, across projects too. Full-text search finds tickets in every project the person can access.
- Bulk toolbar
- Change status, assignee, type, epic, priority, due date and labels, archive, move to another project or delete.
- Saved filters
- Up to 20 personal filters per person, one of them as the default that applies on open.
- Status → In progress
- Add label: Relaunch
- Assignee: Lea Brandt
- Move to project …
What it does not do
So there are no surprises in the demo.
- No sprints or iterations and no sprint planning.
- No swimlanes, no calendar or table view on the board. There is an organization-wide timeline under Planning & reports.
- No free-form workflow designer: the transition rules between status categories are fixed.
Frequently asked questions
- What belongs to a ticket?
- Type (feature, bug, epic or your own), priority, assignee, start and due date, story points, labels, an external reference for the client’s own number and attachments up to 50 MB. Plus subtickets one level deep, links and custom fields where you choose per field whether clients can see it.
- Can we work with milestones and releases?
- Yes. Milestones with due dates and releases (planned, in progress, released, cancelled) are available per project. The feature is off by default and switched on per organization or project.
- Does everyone on the team see every project?
- No. Access comes from project membership, directly or through a team. Clients only see the projects they were invited to.
- How do existing tickets get in?
- Through the importers for Jira, YouTrack, GitLab Issues and CSV. Details are on the Import & integrations page.
Let us talk about how you work.
Spedy is only available through a demo call. Request a demo or book a slot directly.