StoryBoard/Task Branch

User stories

Bug coordinators and developers want to open backporting tasks (to milestone-proposed, to stable branches) as part of a bug story
Release management needs to track what made it to a given milestone and/or final release and point release

Two fields shall be added to tasks:

Branch (defaults to master, can select supported stable branches, can select milestone-proposed in the short periods that is opened): this tracks the branch where the fix shall be proposed and land
Release ("icehouse-3, 2013.1...): this tracks the first milestone or version where the fix landed.

Branch can be selected by the user as part of the task creation. For autocreated tasks, it's set based on the change's target branch.

Release could be set in two ways:

After the fact, as part of the release process: for example when the icehouse-3 milestone-proposed branch is cut, we collect all master-landed fixes without a release set and mark them icehouse-3. When icehouse-3 is published, we collect all the milestone-proposed-landed fixes (if any) and mark them icehouse-3 as well.
At change landing time, by determining the "next" milestone for a given branch (release management would then just adjust what the "next" milestone is for every branch).

Feature stories shall only have "master" tasks since we don't backport features.
We'll need a milestone table for each project, and potentially the ability to group development milestones to form the final release (have a view that shows all dev milestones and RCs will result in showing what ended up in the final release).