[ http://jira.codehaus.org/browse/JBEHAVE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mauro Talevi updated JBEHAVE-358: --------------------------------- Description: In order to get visibility of themes/epics As a release planner I want to be able to map stories by meta filters Using story maps allows us to group stories of cross-cutting concerns, using filters on meta info (JBEHAVE-220). A swimlane view (with one lane per filter) would allow a clear and concise view. was: In order to get visibility of themes/epics As a release planner I want to be able to view stories by theme/epic. Using story maps allows us to group stories of cross-cutting concerns. Themes/epics can be specified directly at story level using Meta info (JBEHAVE-220) Summary: Add Story Mapping with Swimlane view (was: Add Story Map/Theme views) > Add Story Mapping with Swimlane view > ------------------------------------ > > Key: JBEHAVE-358 > URL: http://jira.codehaus.org/browse/JBEHAVE-358 > Project: JBehave > Issue Type: New Feature > Components: Core > Reporter: Mauro Talevi > Fix For: 3.1 > > > In order to get visibility of themes/epics > As a release planner > I want to be able to map stories by meta filters > Using story maps allows us to group stories of cross-cutting concerns, using > filters on meta info (JBEHAVE-220). > A swimlane view (with one lane per filter) would allow a clear and concise > view. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email