Hi @Mike,
A sprint is an entity of its own, a time boxed iteration intended to work with focus on a set of work items (issues). It does not make sense to create sprints inside another sprint.
Nothing prevents you from naming your sprints 1.1. / 1.2 / 1.3 and so on, which is quite common to represents sprints in a program increment. Thus, 2.1 / 2.2 / 2.3 and so on could represent the second increment and so on, without the need of creating a sprint 1 or 2 (which would not contain any issues anyway).
As an alternative, you could consider using fix versions to represent your program increments (the parent level), as they also have start and end dates and are separate from sprints.
Hope this helps!
Hi @Mike ,
No, a sprint means the team can produce a complete incremental delivery.
Sprints can no longer be subdivided into sub-sprints, but you can create different versions and release multiple times in a sprint.
https://support.atlassian.com/jira-software-cloud/docs/what-is-a-sprint/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.