V1 has used containers to express Releases and Sprints then why not replicate that pattern down to the Epic?
Current system assumes that Epic is broken down into child stories, which is a likely case. However for a group of teams it is perfectly feasible that Epic's appear organically as the use case develops across a domain that is otherwise served by multiple teams. When this occurs, one wants the ability to bulk assign stories across and within a project space to an Epic.
Current expression of Epic and Epic board is far too limiting.
by: Tarang P. | over a year ago | Product Planning
Comments
Bulk assignment via multi-select is available on the Backlog page in Product Planning. As of the Winter '13 release, you can also assign existing stories/defects/test sets via the epic details page as well.