Comment 12 for bug 727023

On Sat, Mar 26, 2011 at 3:08 AM, j.c.sackett <email address hidden> wrote:
>> so, this is a problem page for the same reason bugtask:+index is I think;
>> I need to check but I suspect its reusing the same nested > template + per-row view logic
>> - see https://bugs.qastaging.launchpad.net/++profile++show/bugs/cve/2010-4080/+index
>
> You're correct; it uses the bugtasks-nominations-tasks-row template,
> which triggers multiple milestone lookups via a very peculiar function
> in the milestone vocabulary.

It actually seems to be worse than bugtask:+index - probably because
that has lots of partial optimisations and I suspect cve:+index has
been largely ignored.

So we have two tasks:
 - get cve:+index doing the same eager loading bugtask:+index already does
 - fix the milestone pathology in both places.

The latter has had me headdesking when I have looked at it for a
couple weeks, I suspect the right answer is:
 - strip stuff back to bare bones
 - rewrite the vocab on the underlying layer
 - get milestones in the view page using the underlying layer