As a Team Member and Product Owner (respecively) I want a fluent procedure for assigning Bugs to Releases and carrying release notes over to Blog Entries.
- when an Issue is accepted as a Bug, the current Release is set to be affected
- when a Team member sets a Bug to fixed, the next Release is automatically set to be the Fix Release
- no automatic setting is done when some value was already set manually
- Releases have a "Create Blog Entry" action that creates a Blog Entry and populates the contents with a List of Stories from the Sprint and Issues fixed for the Release
2 Story Points
Do, Okt 14, 2010, 05:38 by Casino Club
excellent points and the details are more specific than elsewhere, thanks.