Story Planning

The selectors here provide a way to plan to Releases, Sprints or Kanban.

Mutually Exclusive Planning Fields

Note that some of the selection fields are mutually exclusive.

Sprints are within releases, so planning a story to a sprint will automatically add it to the containing release as well (if it is not already in the release). A story cannot be in both a sprint and a kanban lane at the same time, as these are alternative ways to schedule a story implementation. The story can, however, be in both a release and a kanban lane.

Direct or Indirect Planning

“Direct” planning means that the epic/story is actively planned to a Release, Sprint or Kanban. E.g. by dragging the epic/story into a container in Product Backlog or by editing the planning fields in the epic/story’s “Edit Details” tab.

“Indirect” planning means that the epic/story is indirectly part of a release, e.g. because a parent epic or all the children are planned to the release. You can see if the epic/story is indirectly planned to a release in the epic/story overview.

Edit Warnings

If you e.g. change the existing planning a warning might be displayed. This is only for your information, you are allowed to do this. The warnings only relates to direct planning, not indirect planning.