“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.6
Security problem? Check the security section.
FS#1174 - TODO List for 1.0
Attached to Project:
Flyspray - The bug killer!
Opened by Florian Schmitz (Floele) - Sunday, 28 January 2007, 00:18 GMT+1
Last edited by Cristian Rodríguez R. (judas_iscariote) - Wednesday, 10 June 2009, 01:32 GMT+1
Opened by Florian Schmitz (Floele) - Sunday, 28 January 2007, 00:18 GMT+1
Last edited by Cristian Rodríguez R. (judas_iscariote) - Wednesday, 10 June 2009, 01:32 GMT+1
|
DetailsA list what could/should be done for 1.0
|
Example of user area → notifications.
And notes...
Vote -1
a suggestion: make user-rights translateable (the Permission-List showing up when holding the mouse over the current logged in user at the top left)
My two suggestions:
FS#1040- Close Multiple Tasks at once.Florian..what you think about adding an option like:
“if a task or comment contains an attachment, include it in the email notification too”.
???
You mean send the attachment per mail? That might be a problem if the attachment is large which would cause maybe a lot of additional traffic.
A new templating engine (eval free) was questioned: What about Smarty or phptal?
Smarty: No. Phptal: A possibility, but right now this is rather low priority since the eval-based templates have not caused any serious issues yet.
full compatibility w/ PostgreSQL
ticket #1415
e-mail language depends on sender not recipient =⇒ would it be : "e-mail language depends on recipient not sender" ??? if yes :
no : already exist
it would be nice to be able to create subtasks for a task
Templating Engine: Since I've seen more Zend stuff in the code base, Zend_View might be a good choice. It's not exactly an "engine" in the sense that has it's own language that needs to be parsed or anything like that. It's very, very similar to Savant3 or Solar_View. Good, elegant, and flexible options, in my opinion. These would probably be easier to integrate with the existing code, if the time comes.
Nope, in case we do something, we will move to symfony.
Hi, I noticed above you have "add two check boxes for e-mail notifications" crossed off. I would very much like to add this functionality to my version of flyspray without having to wait for 1.0 (which I am excited about). I would be willing to, at minimum, write up some docs on notifications and managing them – and maybe a few write a more docs going forward. Also, I would propose a seperate issue for the ssl and smtp.
No more update??