Story Planning

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

Mutually Exclusive Planning Fields

Note that some of the selection fields are mutually exclusive. Preplanning is an early grouping of items for a future release, so an epic is typically moved from a preplanning container to a release during the release planning. It cannot be both preplanned and planned to a release at the same time.

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, Kanban or Preplanned. 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. remove an epic from a release by adding it to a preplanning container in the edit form, a warning will be displayed. This is only for your information, you are allowed to do this. The warnings only relates to direct planning, not indirect planning.