[Phpmyadmin-devel] New sf interface
Hi all, I was thinking that it would be quite nice if the "groups" in the new sf tracker were reverse sorted. I mean, who cares about "2.11.9", it's not even supported, it should be bottom of the list. On the other hand, "latest_git" and "3.5.5" are the most likely candidates for a new bug and should be at the top of the list. Is there someone we can ask to fix this? Bye, Rouslan
On Sat, Jan 19, 2013 at 8:04 PM, Rouslan Placella <rouslan@placella.com>wrote:
Hi all,
I was thinking that it would be quite nice if the "groups" in the new sf tracker were reverse sorted. I mean, who cares about "2.11.9", it's not even supported, it should be bottom of the list. On the other hand, "latest_git" and "3.5.5" are the most likely candidates for a new bug and should be at the top of the list.
Is there someone we can ask to fix this?
Bye, Rouslan
On a related note, it would be nice to have a pre-set search with the following criteria status : open or unread owner : none sorted by artifact number in desc order.
This should list the bugs that a developer can work on, in one click. -- Thanks and Regards, Madhura Jayaratne
Le 2013-01-19 11:20, Madhura Jayaratne a écrit :
On Sat, Jan 19, 2013 at 8:04 PM, Rouslan Placella <rouslan@placella.com>wrote:
Hi all,
I was thinking that it would be quite nice if the "groups" in the new sf tracker were reverse sorted. I mean, who cares about "2.11.9", it's not even supported, it should be bottom of the list. On the other hand, "latest_git" and "3.5.5" are the most likely candidates for a new bug and should be at the top of the list.
Is there someone we can ask to fix this?
Bye, Rouslan
On a related note, it would be nice to have a pre-set search with the following criteria status : open or unread owner : none sorted by artifact number in desc order.
This should list the bugs that a developer can work on, in one click.
Madhura, what should be the name of this search? -- Marc Delisle http://infomarc.info
On Sat, Jan 19, 2013 at 10:05 PM, Marc Delisle <marc@infomarc.info> wrote:
Le 2013-01-19 11:20, Madhura Jayaratne a écrit :
On Sat, Jan 19, 2013 at 8:04 PM, Rouslan Placella <rouslan@placella.com wrote:
Hi all,
I was thinking that it would be quite nice if the "groups" in the new sf tracker were reverse sorted. I mean, who cares about "2.11.9", it's not even supported, it should be bottom of the list. On the other hand, "latest_git" and "3.5.5" are the most likely candidates for a new bug and should be at the top of the list.
Is there someone we can ask to fix this?
Bye, Rouslan
On a related note, it would be nice to have a pre-set search with the following criteria status : open or unread owner : none sorted by artifact number in desc order.
This should list the bugs that a developer can work on, in one click.
Madhura, what should be the name of this search?
I'm not really sure. "Fix me", may be?? :)
-- Thanks and Regards, Madhura Jayaratne
Le 2013-01-19 11:41, Madhura Jayaratne a écrit :
On Sat, Jan 19, 2013 at 10:05 PM, Marc Delisle <marc@infomarc.info> wrote:
Le 2013-01-19 11:20, Madhura Jayaratne a écrit :
On Sat, Jan 19, 2013 at 8:04 PM, Rouslan Placella <rouslan@placella.com wrote:
Hi all,
I was thinking that it would be quite nice if the "groups" in the new sf tracker were reverse sorted. I mean, who cares about "2.11.9", it's not even supported, it should be bottom of the list. On the other hand, "latest_git" and "3.5.5" are the most likely candidates for a new bug and should be at the top of the list.
Is there someone we can ask to fix this?
Bye, Rouslan
On a related note, it would be nice to have a pre-set search with the following criteria status : open or unread owner : none sorted by artifact number in desc order.
This should list the bugs that a developer can work on, in one click.
Madhura, what should be the name of this search?
I'm not really sure. "Fix me", may be?? :)
I called it "Todo tickets"; however, I did not find how to restrict to unassigned tickets, or to automatically sort. You can sort by clicking on "#". -- Marc Delisle http://infomarc.info
On Sat, Jan 19, 2013 at 10:23 PM, Marc Delisle <marc@infomarc.info> wrote:
Le 2013-01-19 11:41, Madhura Jayaratne a écrit :
On Sat, Jan 19, 2013 at 10:05 PM, Marc Delisle <marc@infomarc.info> wrote:
Le 2013-01-19 11:20, Madhura Jayaratne a écrit :
On Sat, Jan 19, 2013 at 8:04 PM, Rouslan Placella < rouslan@placella.com wrote:
Hi all,
I was thinking that it would be quite nice if the "groups" in the new sf tracker were reverse sorted. I mean, who cares about "2.11.9", it's not even supported, it should be bottom of the list. On the other hand, "latest_git" and "3.5.5" are the most likely candidates for a new bug and should be at the top of the list.
Is there someone we can ask to fix this?
Bye, Rouslan
On a related note, it would be nice to have a pre-set search with the following criteria status : open or unread owner : none sorted by artifact number in desc order.
This should list the bugs that a developer can work on, in one click.
Madhura, what should be the name of this search?
I'm not really sure. "Fix me", may be?? :)
I called it "Todo tickets"; however, I did not find how to restrict to unassigned tickets, or to automatically sort. You can sort by clicking on "#".
Marc,
status:open AND !assigned_to:["" TO *] seems to work. Can you pls update the search. -- Thanks and Regards, Madhura Jayaratne [1] http://stackoverflow.com/questions/4238609/how-to-query-solr-for-empty-field...
Le 2013-01-19 12:18, Madhura Jayaratne a écrit :
On Sat, Jan 19, 2013 at 10:23 PM, Marc Delisle <marc@infomarc.info> wrote:
Le 2013-01-19 11:41, Madhura Jayaratne a écrit :
On Sat, Jan 19, 2013 at 10:05 PM, Marc Delisle <marc@infomarc.info> wrote:
Le 2013-01-19 11:20, Madhura Jayaratne a écrit :
On Sat, Jan 19, 2013 at 8:04 PM, Rouslan Placella < rouslan@placella.com wrote:
Hi all,
I was thinking that it would be quite nice if the "groups" in the new sf tracker were reverse sorted. I mean, who cares about "2.11.9", it's not even supported, it should be bottom of the list. On the other hand, "latest_git" and "3.5.5" are the most likely candidates for a new bug and should be at the top of the list.
Is there someone we can ask to fix this?
Bye, Rouslan
On a related note, it would be nice to have a pre-set search with the following criteria status : open or unread owner : none sorted by artifact number in desc order.
This should list the bugs that a developer can work on, in one click.
Madhura, what should be the name of this search?
I'm not really sure. "Fix me", may be?? :)
I called it "Todo tickets"; however, I did not find how to restrict to unassigned tickets, or to automatically sort. You can sort by clicking on "#".
Marc,
status:open AND !assigned_to:["" TO *]
seems to work. Can you pls update the search.
Done, thanks. -- Marc Delisle http://infomarc.info
Le 2013-01-19 09:34, Rouslan Placella a écrit :
Hi all,
I was thinking that it would be quite nice if the "groups" in the new sf tracker were reverse sorted. I mean, who cares about "2.11.9", it's not even supported, it should be bottom of the list. On the other hand, "latest_git" and "3.5.5" are the most likely candidates for a new bug and should be at the top of the list.
Is there someone we can ask to fix this?
See https://sourceforge.net/p/allura/tickets/?source=navbar -- Marc Delisle http://infomarc.info
Le 2013-01-19 09:34, Rouslan Placella a écrit :
Hi all,
I was thinking that it would be quite nice if the "groups" in the new sf tracker were reverse sorted. I mean, who cares about "2.11.9", it's not even supported, it should be bottom of the list. On the other hand, "latest_git" and "3.5.5" are the most likely candidates for a new bug and should be at the top of the list.
I am closing all milestones for which all tickets are closed, so at least the list will shrink. -- Marc Delisle http://infomarc.info
Le 2013-01-19 12:09, Marc Delisle a écrit :
Le 2013-01-19 09:34, Rouslan Placella a écrit :
Hi all,
I was thinking that it would be quite nice if the "groups" in the new sf tracker were reverse sorted. I mean, who cares about "2.11.9", it's not even supported, it should be bottom of the list. On the other hand, "latest_git" and "3.5.5" are the most likely candidates for a new bug and should be at the top of the list.
I am closing all milestones for which all tickets are closed, so at least the list will shrink.
Also, "we" should take all older tickets and test if the bug is still in the current stable. If so, move the ticket to the current stable milestone; if not, mark as "closed-out-of-date". But right now, our priority should be to work on bug 3775, a showstopper for 4.0.0-alpha1. -- Marc Delisle http://infomarc.info
participants (3)
-
Madhura Jayaratne -
Marc Delisle -
Rouslan Placella