“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#392 - Add Start date
Attached to Project:
Flyspray - The bug killer!
Opened by Ed Green (edgreen2) - Friday, 15 October 2004, 17:59 GMT+1
Last edited by Florian Schmitz (Floele) - Tuesday, 20 February 2007, 12:22 GMT+1
Opened by Ed Green (edgreen2) - Friday, 15 October 2004, 17:59 GMT+1
Last edited by Florian Schmitz (Floele) - Tuesday, 20 February 2007, 12:22 GMT+1
|
DetailsThere should be a start and end date per task |
This task depends upon
FS#218 - Extensibility mechanism for adding new task properties
View Dependency Graph
View Dependency Graph
Closed by Florian Schmitz (Floele)
Tuesday, 20 February 2007, 12:22 GMT+1
Reason for closing: Implemented in devel
Additional comments about closing: rev 1051 - do it yourself ;)
Tuesday, 20 February 2007, 12:22 GMT+1
Reason for closing: Implemented in devel
Additional comments about closing: rev 1051 - do it yourself ;)
Flyspray already logs the date a task is opened and closed. If this isn’t what you mean, please provide more information.
I think it´s a good idea to have the possibility to enter a start-date for a task.
(This would be the opposite of DueDate)
So the developer see when they have to start working on this task.
For example when a task not already starts so you cannot edit it, the task is disabled (view only).
What do you mean ?
Ed, please post a comment to this task to let us know exactly what you mean.