> - this template I put together is for much higher-level features than
> I'd expect to see as Redmine Features - e.g. the audrey feature I
> wrote up should map to quite a few Redmine features
>From the standpoint of using Redmine to plan releases and convey a roadmap to the
community, I think there is still value in having these high level features listed in
Redmine and showing the sub-features and tasks as children of it. The only rub may be
Redmine if it fails to deal with many levels of relationships. It might handle it fine,
I'm not sure yet.
Redmine should handle as many levels of task nesting as you want with
some restrictions. For example you can't have a feature or scenario
appear underneath a task, etc
-Mo