We're planning for enhanced release management features within Contour and wanted to start a dialog as this comes up quite a bit in our conversations with users.
One common scenario is the need to create a master project with multiple releases that are treated as their own sub-projects. Today there are a couple ways to implement this though we see a need for enhancement.
Create each major release as it's own project
If each release has it's own scope (requirements etc) and time-line etc, we recommend setting up each major release as it's own project at the project home screen. Item's within the sub-projects (major releases) can have trace links defined between items, items can be copied (and soon can be moved across project).
My Project (group)
Release 1 (project)
Requirements
Use Cases
Test Cases
Release 2 (project)
Requirements
Use Cases
Test Cases
Use folders to define releases.
For smaller projects - or an alternative approach is to use folders within the sets of items in a project to define the release. This looks like this...
Use release pick list to define release
A third option is to use the single project configuration and use the release drop down to assign items to releases then use the release view to view items assigned to release. We've been discussing adding filters that enable users to filter by release in the tree - which allows items to retain their hierarchical structure.
We'd like to continue the discussion and find out what you need in this area...
