Hurdle Docs
Go back to Hurdle.dev
  • Introducing Hurdle
  • Integrated or standalone
  • Getting started
    • Workspace setup
      • General settings
      • Managing users
      • Issues
      • Estimates
      • Backlog
      • Workstreams
      • Sprints
    • Integrating with Jira
      • Enabling the integration
      • Field mapping
      • User mapping
      • Common questions
  • Using Hurdle
    • Managing work
      • Projects
      • Issues and subtasks
      • Triage queue
      • Views and filters
    • Backlog refinement
      • Backlog conditions
      • Workstreams
      • Prioritization
    • Sprint planning and tracking
      • Sprint settings
      • Automated planner
      • Adding and removing issues
      • Starting a sprint
      • Active sprints
      • Ending a sprint
      • Completed sprints
Powered by GitBook
On this page
  • Auto-start
  • Manually
  • What happens when a sprint "starts"?
  1. Using Hurdle
  2. Sprint planning and tracking

Starting a sprint

When a sprint candidate has been planned, it's time to start your sprint.

PreviousAdding and removing issuesNextActive sprints

Last updated 1 year ago

Sprints can be started automatically or manually.

Auto-start

You can set a sprint to start automatically by setting a Sprint start day in the .

Manually

To manually start a sprint, click Start sprint at the top of the .

What happens when a sprint "starts"?

When a sprint starts:

  • Unassigned issues are re-assigned to the users to which they've been allocated

  • Issues assigned to one user, but allocated to a different user, are re-assigned

  • Starting sprint metrics are locked in (i.e. allocated issues, allocated points)

If you're , issues assignments and re-assignments will sync when a sprint is started.

Issues can be added or removed from a sprint after it's been started, but changes will impact the scope change metric of the sprint.

sprint series settings
sprint planner
integrating with Jira