in bug lists, fix committed bugs should sort higher

This would be great but we will still need to take in consideration the sheer volume of incomplete bugs and other undecided bugs..

Thanks

On Fri, 2009-08-28 at 22:43 +0000, Vikram wrote:
> This would be great but we will still need to take in consideration the
> sheer volume of incomplete bugs and other undecided bugs..

Of course. When you combine my proposal in bug 420799 with this one I
think it will work well:
 - incomplete bugs will be always near the bottom
 - new bugs with no priority will be at the top for triage

Alright, that does seem to work, you have offered a great idea I have
seen the other bug that you posted and this could offer a change at how
we look at bugs, but I wonder if the new bugs are at the top what about
the critical ones. I think we might have to think of a new way like
putting all the new bugs in a separate page and the direct the traffic
of new bugs there, keeping the critical ones in on a separate page so
developers can keep track of both at the same time

What do you think about that? I will post this idea to the mailing list
talking about this and see how they respond. Thanks again for your idea

Vikram

On Fri, 2009-08-28 at 23:08 +0000, Robert Collins wrote:
> On Fri, 2009-08-28 at 22:43 +0000, Vikram wrote:
> > This would be great but we will still need to take in consideration the
> > sheer volume of incomplete bugs and other undecided bugs..
>
> Of course. When you combine my proposal in bug 420799 with this one I
> think it will work well:
> - incomplete bugs will be always near the bottom
> - new bugs with no priority will be at the top for triage
>
> --
> in bug lists, fix committed bugs should sort higher
> https://bugs.launchpad.net/bugs/420807
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Launchpad Bugs: In Progress
>
> Bug description:
> In bug lists, for a given priority, it would be great if the status was
> also taken into account in the default sort.
>
> The current second-field for sorting is the bug number which isn't
> really that useful.
>
> I propose bugs where there is wasted work waiting to be incorporated,
> before bugs awaiting triager assessment
> before bugs where a developer can start work
> before bugs where a developer is working
> before bugs where user feedback is needed
> before bugs that are fixed
>
> So:
> critical fixcommitted
> critical new
> critical confirmed/triaged
> critical in progress
> critical incomplete
> critical fixreleased
>
> This would make figuring out which bugs I need to poke at next to keep a
> project healthy _so much easier_.
>
> affects malone
>
>
>