Ticket 88 (New)
| Created: | by Sam Lown Sep 11, 2007 |
| Severity: | Assistance Request (2 of 5) |
| Priority: | Low (1 of 4) |
| Attached: |
|
| Assigned: | to no one |
h1. Timeline and email notificat...
Timeline and email notification support
Hi all, with Peter Jones’s blessings, I’m currently working on adding support for Timeline support in Devalot. The idea is that every action in Devalot in the areas of Pages, Blogs and Tickets are recorded in the Timeline with the option of email notification. The two concepts mix well together, so it makes sense to do it this way.
As the first phase of development of this, I’ve internationalised the current Ticket History (instead of storing an array of strings, it now stores an array of hashes where the keys describe the key elements of the update. The view is backwards compatible also.) The information stored in the ticket history will be copied over to the Timeline table in the same format.
In the spirit of OSS, I’d like to request comments and suggestions regarding the timeline and email notification side too see if anyone has any great ideas, or would like to see something special or different, please leave a comment!
Cheers, sam
PS: if you want to try out internationalisation in my Spanish, checkout the devalot trunk and when running, add ”?lang=es_ES” to the end of the URL.
Tags:
Comments:
Have something to say? Login to post a comment.
Sam Lown, Oct 29, 2007
Level 2 (Tourist with 51 points)
I’ve uploaded my latest set of changes to the Devalot subversion trunk containing initial support for the new timeline model and notifications via email. Currently, only Tickets are supported, but I intend to add support for pages, articles, and new member notifications as soon as possible.
Email notifications will only be sent out to the members of a project, and then only if they have selected the ‘receive email’ option in their profile, which is true by default. Every single change to a ticket will be sent to every member of the project, which can result in a large amount of email being sent out. I’m currently thinking of how we can better handle deciding which users receive email, here are some ideas:
Hopefully more to come, and suggestions welcomed.
Please check out the latest svn trunk, its quite stable and indeed I use it in an internal production system.
Cheers, Sam Lown