Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#7777 - Problem with listing closed tasks in Flyspray
Attached to Project:
Arch Linux
Opened by Jens Adam (byte) - Saturday, 11 August 2007, 03:42 GMT
Last edited by eliott (cactus) - Sunday, 02 September 2007, 21:04 GMT
Opened by Jens Adam (byte) - Saturday, 11 August 2007, 03:42 GMT
Last edited by eliott (cactus) - Sunday, 02 September 2007, 21:04 GMT
|
DetailsSince the last Flyspray upgrade it's no longer possible to list closed tasks.
In the past I've used 3 bookmarks for bugs.archlinux.org (one for each project), to automatically list all tasks in chronological order. Now the main Arch Linux project only loads an empty page when I have '&status=' in the URL, but the other two projects are fine. Instead of direct url manipulation it's also the same with clicking the '+' and selecting all tasks. To be honest, I've not verified if it's a known upstream problem, probably because... I wanted to get #7777, w00t! ;] |
This task depends upon
Closed by eliott (cactus)
Sunday, 02 September 2007, 21:04 GMT
Reason for closing: Deferred
Additional comments about closing: I think we are boned on this one.
Sunday, 02 September 2007, 21:04 GMT
Reason for closing: Deferred
Additional comments about closing: I think we are boned on this one.
Much worse thing (for me) is that there's no possibility in new flyspray to list all tasks that are not assigned to developers
(well, it can be worked around by adding a column with assigned developer's name but that's useless for most users and takes space).
I'm closing this as "Deferred". (I hope it will be fixed on next flyspray update).
When you turn on sql loggin, this monstrosity falls out.
SELECT t.*, lc.category_name AS category_name, COUNT(DISTINCT c.comment_id) AS num_comments, COUNT(DISTINCT att.attachment_id) AS num_attachments, p.project_title, p.project_is_active, lst.status_name AS status_name, lt.tasktype_name AS task_type, lr.resolution_name FROM `flyspray_tasks` t LEFT JOIN `flyspray_projects` p ON t.project_id = p.project_id LEFT JOIN `flyspray_list_tasktype` lt ON t.task_type = lt.tasktype_id LEFT JOIN `flyspray_list_status` lst ON t.item_status = lst.status_id LEFT JOIN `flyspray_list_resolution` lr ON t.resolution_reason = lr.resolution_id LEFT JOIN `flyspray_list_category` lc ON t.product_category = lc.category_id LEFT JOIN `flyspray_comments` c ON t.task_id = c.task_id LEFT JOIN `flyspray_attachments` att ON t.task_id = att.task_id LEFT JOIN `flyspray_assigned` ass ON t.task_id = ass.task_id LEFT JOIN `flyspray_users` u ON ass.user_id = u.user_id WHERE t.project_id = 1 AND ( is_closed = '1' ) GROUP BY t.task_id ORDER BY task_severity desc, t.task_id desc, t.task_id ASC;
It seems to return all tasks, not just the ones it shows in the immediate list to the user.
The query takes a while to run as well. My thinking is that it is just too big for the php memory setting, php execution time, or maybe the query is just timing out. Not sure which. I haven't been able to pin it down.
If you limit the search to one category in the 'archlinux' project query dropdown it works. If you add more than one, it seems to puke again.
I think we will just have to live with this one for now.
At some point it might make sense to purge very old tasks..dunno. Are there any really large flyspray installs out there that this works well on? Maybe we have some migration corruption in some of the fields in very old tickets that is causing a problem.