Migrate hero images to responsive set
TaskWEB-126Medium priority
3Priya Nair
Project management, without the complexity
Work moves better with SprintDock.
Plan projects, manage issues, coordinate teams, and ship work — all in one place. More than a task list: sprints, releases, roadmaps and reports stay connected to the work itself.
Projects · Issues · Teams · Sprints · Releases · Workflows
Website Redesign
Sprint 12v2.1.068%
| Issue | Status | Priority | Assignee | Pts |
|---|---|---|---|---|
StoryWEB-124New pricing page layoutdesign | In Progress | High priority | Maya Chen | 5 |
BugWEB-125Nav overlaps content at 768pxfrontend | Review | Highest priority | Daniel Okafor | 2 |
TaskWEB-126Migrate hero images to responsive set | To Do | Medium priority | Priya Nair | 3 |
ImprovementWEB-127Reduce cumulative layout shiftperformance | Done | Medium priority | Lukas Weber | 3 |
TaskWEB-128Write launch checklist in knowledge base | To Do | Low priority | Sofia Alvarez | 1 |
Sample project. Illustrative data, not a customer.
Built for teams that care about how work gets done.
- Software teams
- Product teams
- Design & QA teams
- IT operations
- Customer support
Project
Website Redesign
Progress · 68%
Sprint
Sprint 12Release
v2.1.0To Do
2Write launch checklist
TaskWEB-128Low priority
1Sofia Alvarez
In Progress
1New pricing page layout
design
StoryWEB-124High priority
5Maya Chen
Review
1Nav overlaps content at 768px
frontend
BugWEB-125Highest priority
2Daniel Okafor
Done
1Reduce cumulative layout shift
performance
ImprovementWEB-127Medium priority
3Lukas Weber
Sample project. Illustrative data.
Everything your team needs to move work forward.
From the first idea to the final release, SprintDock keeps planning, execution, and delivery connected.
Projects
Organize teams, workflows, issues, and delivery in one project.
Issues
Turn work into structured issues with priorities, ownership, relationships, and context.
Sprints
Plan focused execution cycles and keep teams aligned on what matters now.
Releases
Connect completed work to real product versions and delivery milestones.
Teams
Coordinate people, responsibilities, permissions, and project access.
Workflows
Build workflows that reflect how your team actually works.
Issue management
Every piece of work has a place.
Capture bugs, tasks, stories, improvements, and custom work types with the context your team needs.
- Configurable issue types, statuses and priorities
- Subtasks, links and blocking relationships
- Comments with @mentions and attachments
- A permanent activity history for every change
Authentication PlatformStoryAUTH-102
Add passkey sign-in for returning users
Returning users can register a passkey after their first password sign-in. Fall back to password when a device does not support passkeys. Acceptance: covered by the QA regression suite.
Subtasks · 2 of 3
- SubtaskAUTH-102-1Registration flowDone
- SubtaskAUTH-102-2Fallback to passwordIn Progress
- SubtaskAUTH-102-3Regression testsTo Do
Attachments
passkey-flow.png · 240 KBthreat-notes.pdf · 88 KB
Comments & activity
- Maya Chen
Maya Chen commented · 2h ago
@Daniel can you review the fallback path before Friday?
- Daniel Okafor
Daniel Okafor changed status To DoIn Progress · 5h ago
- Priya Nair
Priya Nair added to Sprint 12 · yesterday
- Status
- In Progress
- Priority
- High
- Assignee
- Daniel Okafor Daniel Okafor
- Reporter
- Maya Chen Maya Chen
- Milestone
- Authentication Platform
- Sprint
- Sprint 12
- Release
- v2.1.0
- Labels
- securityfrontend
- Story points
- 5
- Estimate
- 2d · 6h logged
Sample project data
Plan work without losing sight of the bigger picture.
An issue can belong to a milestone, a sprint and a release at the same time. Each is its own dimension, so you can regroup work without rewriting it.
MilestoneWhy this work exists
Authentication Platform
- AUTH-101
- AUTH-102
- AUTH-103
- StoryAUTH-101Email verification on sign-upAuthentication PlatformSprint 12v2.1.0
- StoryAUTH-102Passkey sign-inAuthentication PlatformSprint 12v2.1.0
- StoryAUTH-103Session timeout settingsAuthentication PlatformSprint 12v2.1.0
SprintWhen work happens
Sprint 12
- AUTH-101
- AUTH-102
- AUTH-103
ReleaseWhat gets delivered
v2.1.0
- AUTH-101
- AUTH-102
- AUTH-103
Milestone, sprint and release are separate fields on each issue. Moving an issue to another sprint does not change its milestone or release, and a release can include work from many sprints.
Sample project data
Turn plans into visible progress.
Kanban and Scrum boards show where every issue stands. Select a card to move it one column forward, the way a drag does in the app.
Sprint 12 · 1 of 5 done
Backlog1
To Do1
In Progress1
Review1
Done1
Sample project data
Plan the next sprint in minutes.
Rank the backlog, pull work into a sprint, and see the committed points as you go. Try it: add and remove issues below.
Backlog
3 issues · 8 pts- StoryAUTH-108Remember trusted devicesMedium priority5Maya Chen
- BugAUTH-109Reset link works twiceHighest priority2Daniel Okafor
- ImprovementAUTH-110Clearer sign-in error messagesLow priority1Sofia Alvarez
Sprint 13 Future
3 issues · 11 pts- StoryAUTH-101Email verification on sign-upHigh priority3Priya Nair
- StoryAUTH-102Passkey sign-inHigh priority5Daniel Okafor
- TaskAUTH-103Session timeout settingsMedium priority3Lukas Weber
Sample data. In SprintDock you can also drag issues between the backlog and sprints.
Releases
Know what you're shipping.
Releases track what gets delivered. Sprints track when the work happens. SprintDock keeps the two separate and connected.
v2.1.0
UnreleasedRelease date · October 18, 2026
74%
- 50
- Issues
- 37
- Completed
- 13
- Remaining
- AUTH-101Email verification on sign-upSprint 11Completed
- AUTH-102Passkey sign-inSprint 12Remaining
- PAY-214Retry failed card paymentsSprint 13Remaining
Sample project data
Sprint
When work happens
A time-boxed cycle. Work is committed at the start and unfinished issues move on when it completes.
Release
What gets delivered
A product version with a date and a set of issues. Work from several sprints can ship in one release.
See where the work is going.
A strategic timeline of milestones and the releases they land in, separate from the day-to-day board.
Q4 2026 · Milestones
OctNovDec
MilestoneAuthentication
◆ v2.1.0
MilestonePayments
◆ v2.2.0
MilestoneReporting
◆ v2.3.0
MilestoneMobile Experience
Milestone Milestone timeline◆ Release
Sample roadmap. Dates and milestones are illustrative.
Give every team the right level of access.
Organization, teams, projects, members, roles and permissions are separate concepts, so access stays predictable as you grow.
Acme Studio (sample organization)
- Frontend TeamMaya ChenDaniel OkaforWebsite Redesign
- Backend TeamLukas WeberPriya NairWebsite Redesign
- QA TeamSofia AlvarezPriya NairWebsite Redesign
- Design TeamMaya ChenSofia AlvarezWebsite Redesign
Fictional people and teams.
Three different things
- Team membership
- Who belongs to a group, such as Frontend or QA.
- Project membership
- Who can open a project, and with which role.
- Issue assignment
- Who is responsible for a single piece of work.
Built-in roles, with custom roles when you need them
Project Manager
Plans and runs projects, sprints and releases.
Developer
Works on issues.
QA
Tests and verifies issues.
Viewer
Read-only access.
A member's organization role can be extended per project.
Find the work that matters.
Write a query, save it as a filter, and share it. Every filter can be reused in the issue list and on dashboards.
project = WEB AND status = "In Progress" AND assignee = currentUser() ORDER BY priority DESC
- Project
- Issue type
- Status
- Priority
- Assignee
- Sprint
- Release
- Milestone
- Labels
- WEB-124New pricing page layoutSprint 12Maya Chen
- WEB-133Update footer link structureSprint 12Maya Chen
- WEB-136Fix focus order on mobile menuSprint 12Maya Chen
Sample project data
Understand progress without chasing updates.
Dashboards and reports are computed from the issue history, so numbers match what actually happened.
Sprint velocity
S8
S9
S10
S11
S12
Committed pointsCompleted points
Sprint 12 issues
17 / 25
completed · 8 remaining
Release progress
v2.1.074%
37 done · 13 remaining
Cycle time
3.4 days
average from In Progress to Done
Work distribution
- Maya Chen7
- Daniel Okafor6
- Priya Nair5
- Lukas Weber4
- Sofia Alvarez3
Sample data. The app also includes burndown, burnup, cumulative flow, created vs resolved and control charts.
Keep the context with the work.
Teams should not have to search across disconnected tools to find out why a decision was made. Documentation, discussion and files live next to the issues they explain.
Version 4 · edited by Maya Chen
Passkey sign-in: design notes
Users register a passkey after a first password sign-in. Devices without support keep using passwords.
Linked issues
- StoryAUTH-102Passkey sign-in
- StoryAUTH-103Session timeout settings
Sample project data
Knowledge base
Project documentation with version history and restore, visibility by team or project, tables, code blocks and images.
Issue links & relationships
Link, block and relate issues, break them into subtasks, and follow the chain from milestone to release.
Comments & activity
Discussion with @mentions and reactions beside a permanent record of every change.
Attachments
Files on issues, comments and pages, validated on upload and stored with the work.
Forms
Structured forms that turn answers into issues, for your team or through a public link.
Customer portal
An optional portal where customers raise and follow tickets. Internal comments and staff details stay hidden.
Access you can reason about.
Clear boundaries between organizations, projects, teams and roles.
Organization-level access
Every request is checked against the caller's organization membership.
Project-level access
Roles can be extended per project, so people see only the projects they belong to.
Roles & permissions
Built-in roles plus custom roles with fine-grained permissions.
Audit trail
Issue history is append-only, and organization audit logs record administrative actions.
Project isolation
Dashboards and portal views are computed for the viewer, so sharing never exposes data they cannot see.
Safe file handling
Uploads are checked by type, signature and size, and served with restrictive headers.
From plan to release in three steps.
- 01
Plan
Create projects, define work, and organize priorities.
- 02
Execute
Run issues, boards, teams, and sprints.
- 03
Deliver
Track releases, progress, and outcomes.
Your team's work deserves a better system.
Bring projects, issues, teams, planning, and delivery together with SprintDock.