Opened 3 months ago

Last modified 3 months ago

#13943 assigned Task/To do item

Receive notifications for new tickets from Trac

Reported by: https://id.mayfirst.org/jaimev Owned by: https://id.mayfirst.org/jaimev
Priority: High Component: Tech
Keywords: trac Cc: https://id.mayfirst.org/jamie
Sensitive: no

Description

Under our current setup Trac does not send any notification to the support team when a new ticket is created. It only does so once that ticket is assigned to you or if you have been added to the cc field.

I have always wanted to receive immediate notifications for any new ticket created but that option is not available.

There is an option to assign an address to the 'smtp_always_cc' variable in the trac.ini wich send notifications for all activity under all conditions however that seems like overkill.

It looks like the behaviour I am looking for has been added as the INotificationSubscriber in Trac release 1.2.3 which is not even in Debian unstable. However this subscriber was originally implemented as a single file plugin and can be added directly to the Trac plugins folder.

https://trac.edgewall.org/wiki/CookBook/Notification/Subscriptions#Subscribetonewcreatedtickets

I would like to try this.

Change History (2)

comment:1 Changed 3 months ago by https://id.mayfirst.org/jaimev

  • Owner set to https://id.mayfirst.org/jaimev
  • Status changed from new to assigned

I was reading the above documentation incorrectly. The cookbook recipe above is a single file plugin that add functionality that has already been included in Trac release 1.2.3. However it "implements" the INotificationSubscriber api functionality which was only added to Trac since version 1.1.3

So still unavailable until we upgrade moses to stretch.

What are the considerations for that upgrade?

comment:2 Changed 3 months ago by https://id.mayfirst.org/jamie

I think upgrading moses would be great.

Here are some considerations:

  • trac uses postgres - which means standard postgres upgrade steps (which are pretty well documented here #11583).
  • we currently maintain a few custom plugins which are maintained in a git repo. Of the three I see there, emailnotset warning seems to be the only one that matters (it causes your preferences link to blink if you have not set an email address). The emailorlogin required plugin is no longer relevant because we now require a login to post tickets. And, I'm not sure we have ever used the scheduleworkflow plugin
  • We have some customizations in htdocs which should not be a problem
  • We have some customizations in templates, which could cause problems if the base templates have changed (only site.html seems to be in use).

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.