too many clicks to get to important review

[Robert Collins]

Reviews are always for branches [in launchpad], and branches are
often[not exclusively] for specific bugs.

Yet, starting with a bug in our 2.0 list, I had to click:
 to get to the bug
 to get to the branch
 to get to the review

It would be great if this was more streamlined.

One way might be to have a link directly to the merge on the bug list.
That is when showing the branch symbol in the bug list, if there is a
review, make the symbol take you to the review. Or something.

There are probably a tonne of interesting interactions with milestones
(e.g. our 2.0 milestone is probably on the wrong series etc, but thats
fixable).

-Rob

 affects launchpad-code

[Paul Hummer (rockstar)]

I think a derived status based on whether or not there's a merge proposal would be the order of the day here.

[Robert Collins (lifeless)]

On Sat, 2009-10-10 at 03:13 +0000, Paul Hummer wrote:
> I think a derived status based on whether or not there's a merge
> proposal would be the order of the day here.

I don't understand how that would help

-Rob

[Tim Penhey (thumper)]

On Mon, 07 Sep 2009 09:31:52 Robert Collins wrote:
> Public bug reported:
>
> Reviews are always for branches [in launchpad], and branches are
> often[not exclusively] for specific bugs.
>
> Yet, starting with a bug in our 2.0 list, I had to click:
> to get to the bug
> to get to the branch
> to get to the review
>
> It would be great if this was more streamlined.
>
> One way might be to have a link directly to the merge on the bug list.
> That is when showing the branch symbol in the bug list, if there is a
> review, make the symbol take you to the review. Or something.

we are looking to link the active code review for a linked branch on the bug
page.

[Tim Penhey (thumper)]

Rob, do you think this is OK now?