Velo PlannerCOMING SOONCapacity-aware planning with drag-and-drop prioritization. Visualize team workload across sprints, track blockers, manage epic timelines and monitor sprint health — all without leaving Jira.
EXAMPLE DATA · JIRA · SPRINT PLANNING
Sprint 24 — 3 sprints planned
SPRINT 24
32 pts
88%
SPRINT 25
18 pts
52%
BACKLOG
47 pts
unallocated
3 membros · 10d úteis
0 blockers
What Velo Planner does
Why Forge-native
No data leaves your Atlassian tenant. No proxy layer. No "trust us, the data is encrypted in transit."
Your data stays in the region your Atlassian contract specifies. No cross-border transfers.
The UI adapts to the user's Jira language automatically. No configuration required.
Inherits your Jira permissions, groups and SSO. No parallel admin to manage.
FAQ
Does it work in any Jira project?
Yes, in company-managed and team-managed projects with Sprints turned on.
Does my data leave Jira?
No. Velo Planner runs entirely on Atlassian Forge. No data goes to outside servers.
Can I control who edits the plan?
Yes. Access is set by Jira role, group or individual user.
Does it work in dark mode?
Yes. It follows the Jira theme and adapts its colors.
How many sprints can I plan at once?
The grid shows up to 4 sprints at a time. The backlog stays available on the side.
Forge-native. No external accounts. No data leaving your Atlassian tenant.