Bug deadlines (or bug 103636)

[Christian Robottom Reis]

On Tue, Jul 27, 2004 at 05:06:43PM -0700, Joel Peshkin wrote:
> Deadline is one of many fields of this general category that coudl be 
> handy.  In my own site, we have a "snooze date" which is only visible to 
> the development team (not the customer) and used to indicate that work 
> on this will not BEGIN until that date passes (and I dont want to be 
> whined at).

Okay, but generally speaking this is a much less frequently-encountered
feature on commercial bugtracking systems than a target date.

> This would be a handy field, but should be only enabled if a param is 
> set.  Ideally, it should be possible to indicate which users can see and 
> use the deadline.

Sure. But isn't grouping it together with timetracking the correct
way to do this? AFAIK informing the viewer of how much time has been
worked on a certain bug is certainly more sensitive than the date we
expect to have it fixed, right?

Implementing this as a custom field forbids us from doing smarter
analysis on the time-based information we're already collecting as part
of TT. The extra field is hardly considerable as bloat.

Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 2331