Draft · not indexed. Part of what this page describes is not generally available yet.
For IT service firms
Tickets are quick to create. A sprint that holds needs capacity.
IT service firms juggle projects, maintenance and ad-hoc requests. Peak One orders them on the board and, if you want, plans them in sprints with an eye on capacity.
Try it
Plan a sprint
Sample data · nothing is saved- 5 P
- 3 P
- 8 P
- 2 P
- 5 P
0/13 points
Fits the velocity. Sprints with burndown are beta in Peak One.
Interactive demo with invented sample data. No account, nothing is saved or sent.
How it works
A board with your statuses
New, in progress, review, with client, done: the board is available today.
Sprints with burndown (beta)
Sprints exist in Board V2, part of Work V2 and not in the app catalog yet.
One task for everyone
The ticket in the sprint is the same task in the calendar and in My Day. There is no second list.
Honest limits
Sprints are beta
Board V2 with sprints is built but not in the app catalog yet.
Not a ticket system for end customers
This page covers project work in the team. Peak Helpdesk is a separate app.
Imports not switched on everywhere
The Jira import is built but not switched on everywhere yet.
Frequently asked questions
Do I have to use sprints?
No. The board works without sprints. Sprints are a beta option in Board V2.
Can I move over from Jira?
An import is built but not switched on everywhere. Check first whether it is available to you.
Does the client see our tickets?
Only a snapshot you release (beta). Peak sends clients nothing on its own.
Fewer interruptions, sprints you can rely on.
Start with a board and add sprints when you need them.
Start free