On Mon, Mar 01, 2010 at 08:21:18AM -0000, Tim Penhey wrote:
> On Mon, 01 Mar 2010 17:17:09 Deryck Hodge wrote:
> > Public bug reported:
> >
> > I've done a hackish fix to have a method return None on max_bug_heat for
> > IPerson, but this needs a proper fix with a DB patch. This bug is a
> > reminder that this should be done ASAP after 10.02.
>
> I strongly suggest that you don't do this unless there is a really
> good reason for a person or team to have a max_bug_heat.
I agree. Think of the UI if this is done. You look at your listing and
see a bug that looks really hot. Now you click on it, go to the bug
page, and suddenly it's not hot anymore, because it's not hot in the
project context?
On Mon, Mar 01, 2010 at 08:21:18AM -0000, Tim Penhey wrote:
> On Mon, 01 Mar 2010 17:17:09 Deryck Hodge wrote:
> > Public bug reported:
> >
> > I've done a hackish fix to have a method return None on max_bug_heat for
> > IPerson, but this needs a proper fix with a DB patch. This bug is a
> > reminder that this should be done ASAP after 10.02.
>
> I strongly suggest that you don't do this unless there is a really
> good reason for a person or team to have a max_bug_heat.
I agree. Think of the UI if this is done. You look at your listing and
see a bug that looks really hot. Now you click on it, go to the bug
page, and suddenly it's not hot anymore, because it's not hot in the
project context?