[Collaboa] time estimates

[Tom Clarke]

On 2/21/06, Waldemar Kornewald <wkornew at gmx.net> wrote:
> Tom Clarke wrote:
> > I sincerely hope we can resolve these issues, as we will all benefit
> > from more people collaborating on the ticket interface, which I agree
> > is the central feature around which everything else fits.
>
> Well, I thought about milestones some more...
> If used correctly they do exactly what they should. If you start
> assigning tickets to multiple small milestones you'll soon have to
> reschedule them. So, we should release a brief "best practice" or
> "use cases" document with examples of how to manage your tickets
> effectively. For example, you should never put too many tickets into a
> minor milestone since you'll soon have to reschedule them. Only place
> the most *critical* tickets into a milestone and leave the rest in a
> ticket buffer milestone (e.g.: "V1 future").

Well, I can't say that we've had the problem where tickets get
endlessly rescheduled. We use the milestones to map out a roadmap of
what features will be in each released and they stay mostly
consistent, a little increasing of priority here, a little decreasing
of priority there.

> Anyway, let's go with milestones. The ticket creation form should not
> allow for selecting milestones and priority, though (maybe depending on
> role those fields can still appear?).

It should be there.. but yes, it should depend on role.

> Next to the description/details field Problem reports should also have a
> little checklist
> * how to reproduce
> * expected behaviour
> * experienced behaviour

I like!

> I hope that this issue can be closed, now.

:-)

-Tom