Flyspray - The bug killer!

  • Status Planned
  • Percent Complete
    0%
  • Task Type Feature Request
  • Category Database Queries
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Defer
  • Reported Version 1.0 devel (github master)
  • Due in Version 1.1 devel
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray - The bug killer!
Opened by ack - 17.06.2012
Last edited by peterdd - 09.03.2015

FS#1748 - Sort by recent activity

It would be great to sort the task list by recent activity. This would mean any change to an issue, including new comments, would rise to the top. This would make it easy to keep up on recent discussion even if you don't want to get every single detail via notifications.

Project Manager
peterdd commented on 09.03.2015 10:26

While using bug.flyspray.org as new developer I think this should be implemented in 1.0.

There is the event log. If we add a

group by task_id

and

sort by date desc

this should be not too hard to implement.

Project Manager
Psychokiller1888 commented on 09.03.2015 13:53

Yeah, we have time till feature freeze anyway... You're up for it?

Project Manager
peterdd commented on 11.03.2015 17:25

Currently jahto is working on the eventlog and default_order_by.

I added a comment to the introduction of default_order_by field on github commit.

I will look currently at other open tasks.

Project Manager
Psychokiller1888 commented on 11.03.2015 17:29

I implemented default_order_by

Project Manager
peterdd commented on 11.03.2015 17:36

Sorry.

Lets discuss default_order_by:

I haven't tested yet, but maybe size="30" will be too short in future if the order by consists of multiple fields. Imaging I prefer for example this order:

ORDER BY supertask_id DESC, priority ASC

Maybe we can use the tpl_double_select() for letting the user choose their default orderby?

On the left side of the double_select this:
field1 ASC
field1 DESC
field2 ASC
field2 DESC
....
and so on.

Project Manager
Psychokiller1888 commented on 11.03.2015 17:41

No, don't be sorry, wasn't meant to be: I, ME, PSYCHO, implemented it. I quickly wrote it from my phone to say it is implemented already.

By implementing it, I actually dropped the second order by that FS proposes, i mean in the config. You can only choose the order1. I chose 30 because the name columns to go over 20, let's space. The order_by will never be greater than the greatest column name. I didn't implement default_sort_by.

If i understand your question correctly, you'd like to allow an advanced default_order_by?

Project Manager
peterdd commented on 11.03.2015 18:28

Yes.

To be clear: FS#1748 "Sort by recent activity" and "default_sort_by" are different tasks, I know.

If you only add a field_name to default_order_by, do we sort ASC or DESC? How the user should know?

I would vote for to storing the whole personal ORDER BY part into this field.
As user interface on myprofile for that we can use the tpl_double_select().

The serverside form handler then validates the values (only existing allowed columns + ' ASC/DESC') of this tpl_double_select() and joins the parts together with join(", ", $validatedOrderByArray);
Check length of resulting orderby-string before saving!

So lets change that field size to 255?

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing