Flyspray - The bug killer!

“If debugging is the process of removing bugs, then programming must be the process of putting them in.” – Edsger Dijkstra

This is the Bug Tracking System for the Flyspray project. This is not a demo! Before opening a new task, please read the guidelines!

Do not issue bugs reports against versions earlier than 0.9.9.5

Security problem? Check the security section.

Tasklist

FS#728 - Default sort column for projects

Attached to Project: Flyspray - The bug killer!
Opened by Adrian Tanase (Adi) - Wednesday, 09 November 2005, 12:28 GMT+1
Last edited by Florian Schmitz (Floele) - Sunday, 03 December 2006, 00:30 GMT+1
Task Type Feature Request
Category User Interface
Status Closed
Assigned To No-one
Operating System All
Severity Low
Priority Normal
Reported Version 0.9.8
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

As I usually want to track the bugs by the opening date, I would really like an option to set the default sorting of the list, not just the columns that appear. I believe this to be just as useful as the Default Project option. It could be implemented sitewise or as a per project option.

Closed by  Florian Schmitz (Floele)
Sunday, 03 December 2006, 00:30 GMT+1
Reason for closing:  Implemented in devel
Additional comments about closing:  rev 899
Comment by Anders Betner (flymehome) - Wednesday, 09 November 2005, 13:04 GMT+1

An even better option would be to have the sort order be persistent per user. If you sort by column bla bla then the list will be sorted by that column the next time you return to the list. That way we don’t have to add more options to the config.

Comment by Tony Collins (knigits) - Wednesday, 09 November 2005, 13:23 GMT+1

Agreed. I don’t want Flyspray over-optioned, and this sounds like a convenient thing to remember. Perhaps ‘my last search’ could be what is shown when the user first re-opens Flyspray?

Comment by Adrian Tanase (Adi) - Wednesday, 09 November 2005, 13:57 GMT+1

Anders, even better. Tony, I believe that we should keep the sorting separate from the ‘my last search’ feature, since I expect to see my tasks sorted the same way even when I switch projects, something where ‘my last search’ isn’t valid anymore.

Comment by Anders Betner (flymehome) - Wednesday, 09 November 2005, 14:47 GMT+1

Why not remove the ‘my last search’ from the menu and use that code to make the last thing you did on the task list persist no matter what you do. Including whatever search term I have entered.

Comment by Pierre Habouzit (MadCoder) - Wednesday, 09 November 2005, 15:21 GMT+1

because it badly sucks when you browse in multiple tabs. not that it’s already the case anyway.

note also that it’s a dupe  FS#479  but since there is more comments here, I’ll close the old one

Comment by Anders Betner (flymehome) - Wednesday, 09 November 2005, 15:27 GMT+1

But I though ‘My last search’ used the url and not the session or cookies to know what happend last. I do admit I haven’t checked the code thoug.

Comment by Pierre Habouzit (MadCoder) - Wednesday, 09 November 2005, 15:36 GMT+1

actually my last search uses the database.
what uses the session is the <prev task | next task>

I just went trhough 75% of the tasks of flyspray’s BTS, needing to do some custom search in the middle, and that completely broke the navigation many times. it’s *very* irritating. and it’s exactly the kind of “persistent” order that is suggested.

we have to be more clever when it comes to navigation, curent solution is un-intuivitive and will really make users that does not know the code that flyspray is completely broken, whereas it’s relatively minor.

Comment by Adrian Tanase (Adi) - Wednesday, 09 November 2005, 15:47 GMT+1

I agree, I keep thinking about ways to clarify the persistence of search, navigation and It’s tought as is right now. I promise I’ll give it some thought and post back to this topic.

Comment by Mac Newbold (macnewbold) - Wednesday, 09 November 2005, 17:34 GMT+1

If we’re making the default sort customizable, should there be a global default and a per-project default, too? Or is it just a per-user default that we should have? (I’m not trying to promote anything but per-user at this point, because I’m not sure what the benefits would be, so I wanted to bring it up.)

Comment by Pierre Habouzit (MadCoder) - Wednesday, 09 November 2005, 17:44 GMT+1

default sort is definitely per user.
but I’m not sure what’s the best thing to do here given to the navigations problems I mentionned

Comment by Florian Schmitz (Floele) - Sunday, 03 December 2006, 00:30 GMT+1

This is implemented in 1.0 devel now. We have to look into the navigation issues during 1.0 development seperately.

Loading...