Another rather important feature came to my mind that we currently depend on.
Mail notifications should be template based with variables or some placeholders for ticket properties. Tickets should therefore probably get a CC field.
Currently, we have different templates for different actions (Create, Resolve, Comment).
I think we should discuss that a little bit more in detail. What is the desired output and what would be an overkill? I think that this is something rather specific and should definitely be realised as an extension.
There are many unaswered questions. Maybe you could describe this task a little bit more in detail.
Registered users always need to supply an e-mail address. Maybe right now this e-mail address isn’t validated but that would be a secondary problem.
If I only give registered users access to the retrospectiva system, let’s suppose they all have valid e-mail addresses.
Our workflow is as follows:
Although my description detailed our specific workflow, I think commenting on a ticket should work a bit like a discussion on Slashdot (without the trolls ;-) in the sense that I’m notified whenever someone replies to my ticket.
In general, as soon as you use the ticketing system in a large enough context it gets extremely difficult to keep track of all changes. Mail notifications make that significantly easier.
In short:
You want registered users to be able to “subscribe” to tickets, so they can get a notification, when something has changed. Of course they should be able to ‘unsubscribe’, eg. when the ticket does not interest them anymore.
Using the CC field a user could subscribe to the ticket or unsubscribe. I would like to configure notifications on a per-system level too. Requesters and owners are always subscribed.
Duplicate of [#37]