Flyspray - The bug killer!

  • Status New   Reopened
  • Percent Complete
    30%
  • Task Type Feature Request
  • Category User Interface
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version 0.9.9-devel
  • Due in Version 1.1 devel
  • Due Date Undecided
  • Votes 3
  • Private
Attached to Project: Flyspray - The bug killer!
Opened by Martin Marconcini - 17.08.2006
Last edited by peterdd - 06.03.2015

FS#1040 - Close Multiple Tasks at once

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 ;)
It would be nice to have to option to select all the tasks you want to close, and that the "popup" when you enter the reason/etc, applied to all the tasks I selected...

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

Admin
Florian Schmitz commented on 17.08.2006 15:03

Sounds reasonable, should probably implemented together with a mass edit feature.

Martin Marconcini commented on 17.08.2006 15:35

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) ;)

Premek Brada commented on 26.02.2007 20:16

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.

Project Manager
peterdd commented on 06.03.2015 22:27

Reopened. We disabled the feature for 1.0, because there must be made some checks done before closing or moving tasks with subtasks, dependencies.

We plan to reenable this feature for FS1.1 or FS1.2, when mass operations is stable implemented.

Project Manager
peterdd commented on 01.10.2015 15:33

Before doing any bulk close action, each task must be checked if it is legit to close it. (user permission, blocked by dependencies, ..)

If there is any problem, the same tasklist form with all the selected tasks should be reshown and the user should be informed which tasks are the reason for the deny.
(highlighting the rows in the tasklist or a message listing tasks and reasons)

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing