I started looking at this today, and it seems to me that the easiest
approach to this would be to "rename" project to release and create
another entity that would be able look across projects.
In other words this new product entity would have a backlog and
releases. The releases would have their own backlogs and priorities.
What do you think?
Mauro
On Jan 9, 9:34 am, "Jake Dempsey" <
angelo0...@gmail.com> wrote:
> Absolutely!
>
> I put releases in there but never got a chance to do anything with
> them....for now they are really just metadata. The idea was to provide a
> nice release planning interface (drag and drop) which would allow you to
> quickly assign stories to releases and move stories from one release to
> another.
>
> On a side note...eXPlainPMT needs a refresh. With Rails 2.0 out we really
> need to comb the app and make it restful and refactor alot of old
> stuff.....time time time.
>
> Jake
>
> On Jan 8, 2008 8:02 PM, mabotelh <
mabot...@gmail.com> wrote:
>
>
>
> > I see that releases and milestones currently are just dates in the
> > calendar.
>
> > Is there any interest (besides mine off course), to have stories
> > assigned to a release?
>
> > The process we follow is to assign stories to a project and then
> > schedule a release with a subset of the backlog. The iterations are
> > then planned out of the release backlog.
>
> > Mauro
>
> --
> Jake
Dempseywww.watij.comwww.explainpmt.com