On 16/03/15 13:30, Ron W wrote:
On Sun, Mar 15, 2015 at 3:56 AM, Graeme Pietersz <[email protected]
<mailto:[email protected]>> wrote:
No one system has all these, but looking at multiple ticket
trackers, the obvious things to me are:
1) email notifications, the most important for me
Can currently be accomplished with external (to Fossil) service,
using, for example, Fossil's RSS feed to trigger email generation.
Using RSS does not really work, not only because of the problems with
private repos, but because it does not allow users to choose which
tickets they get notifications about.
Is it possible with some customisation of the tables (adding a table to
store which users wants notifications of which tickets) and a script
(there is a ticket change hook now?).
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
