“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.
FS#1040 - Close Multiple Tasks at once
Opened by Martin Marconcini (gryzor) - Thursday, 17 August 2006, 16:46 GMT+1
Last edited by Florian Schmitz (Floele) - Monday, 26 March 2007, 17:13 GMT+1
|
Details
We don’t close the tasks until the release is “made”, that is we let them under “Requires Testing” with 100% complete. When the release/testing cycle is finished, somebody has to go task by task, and start closing them... it’s a PITA ;) I recall reading something about this in the past, but haven’t found it; and if this is implemented, I haven’t seen a way to do it in 099beta1 |
Monday, 26 March 2007, 17:13 GMT+1
Reason for closing: Implemented in devel
Additional comments about closing: rev 1124
Sounds reasonable, should probably implemented together with a mass edit feature.
Not being very proficient with PHP nor the innerworkings of Flyspray, I imagine that the “close tasks” drop down, should bring a box just like the one when you press “close task” in the task detail. After you fill in the details (reason, comments for closing, etc.), pressing close task should perform a while (tasks) { DoClose(); }
(Excuse me for my poor pseudo-code) ;)
I’ve just voted for this one. Would add: please not only batch close, but also batch assign, change priority, due-in-version and possibly other fields; similarly like e.g. Mantis (www.mantisbt.org) does. It’s extremely useful when you (or a Change Control Board, or project manager) need to manage a task list.