Sprint, backlog and epic planning
Jira-style planning without Jira.
- Backlog, multiple active sprints, epics and sub-tasks
- Estimates, versions and release notes
- Move unfinished work to another sprint or back to the backlog when a sprint ends
Sprints & planning
Sprints, backlogs and epics, the way your team already works
Jira-style backlogs, multiple active sprints, epics, sub-tasks, estimates and versions, with burndown, velocity and time against estimate.
| Sprint | Estimated | Logged | Variance | Tickets |
|---|---|---|---|---|
| Sprint 14 · active | 62h | 58h 30m | −3h 30m | 18 |
By status
By type
Quick answer
Jonta has a Jira-style backlog with multiple active sprints, epics, sub-tasks, estimates and versions. When a sprint ends you choose where unfinished work goes, and burndown, velocity and time-against-estimate reports show how the sprint went.
Reporting and audit trails
Progress and accountability in one place.
- Burndown, velocity and work breakdowns
- Delivery metrics and time-in-stage reporting
- Time against estimate by sprint
- An audit log you can export to CSV
Project-specific configuration
Every client engagement is set up its own way.
- Ticket numbering, workflow and board configuration per project
- Project team and client-facing columns
- Time tracking switched on or off per project
Included on every plan: Free, Pro and Enterprise. See pricing.
Questions about Sprints & planning
Can we run more than one sprint at once?
Yes. Jonta supports multiple active sprints, which suits agencies running several client projects side by side.
What happens to unfinished tickets at the end of a sprint?
When you complete a sprint you choose whether unfinished work moves into another sprint or goes back to the backlog.
More Jonta features
Try every feature free for up to 5 users.