Projects should have an owner for default notifications

[nielo]

Like components projects should offer an owner field which holds the project's maintainer. If a new ticket come's without component and assignee, no notification is send.

[falkb]

If a new ticket come's without component and assignee, no notification is send.

Do you mean in this case the project owner should get the notification?

[nielo]

Yeah. Don't you think it would be nice and fits realistic needs?

[anonymous]

It's quite special, I'm not sure. I can easily imagine team leaders who don't want that, including some here. :) Maybe it's better the other way round that they subscribe to emails coming from this project. The question is how easy it is to convince the announcer plugin to offer project-wise...

[nielo]

Replying to anonymous:

It's quite special, I'm not sure. I can easily imagine team leaders who don't want that, including some here. :)

And they do argue how?

[Ryan J Ollos]

With Trac 1.2 you could create a notification subscriber, similar to the Component subscriber proposed in ​trac:#11870. If someone creates the component (i.e. plugin), I suggest adding it to SimpleMultiProjectPlugin and use an extras_requires so that's it's only available for Trac >= 1.2: ​browser/tags/trac-1.0.13/setup.py#L105.

There's no maintainer for AnnouncerPlugin and generally it only supports components in Trac, so support is unlikely to be added there.

Also, you can set [ticket] default_component: TracIni#ticket-section, and it's also possible to set the default_owner. I understand that is restrictive, but I just wanted to provide it as workaround of limited utility.

[nielo]

Okay, thx.

[Ryan J Ollos]

I'm happy to help if you need any suggestions or code review. ​trac:#11870 would be a good template to start with.

[falkb]

As stated here I'm just around for bugfixes in the medium term. You could ask Cinc-th if he's willing to add such a patch since it sounds quite straightforward what to do for the AnnouncerPlugin. In any case I wouldn't suggest to switch to "email to project owner" by default but as option.

Hmm, well, I haven't rights to add Cinc-th as CC for this ticket.

[nielo]

Replying to falkb:

In any case I wouldn't suggest to switch to "email to project owner" by default but as option.

Why?

To clarify my point: if we do use projects instead of components to organize our companies trac environment (because we want your wonderful extra candy like differing milestones and timeline) and a ticket author does not know the person to assign but does know the project, who should get notified about the new ticket if not the project's owner?

[falkb]

Replying to nielo:

Replying to falkb:

In any case I wouldn't suggest to switch to "email to project owner" by default but as option.

Why?

To clarify my point: if we do use projects instead of components to organize our companies trac environment (because we want your wonderful extra candy like differing milestones and timeline) and a ticket author does not know the person to assign but does know the project, who should get notified about the new ticket if not the project's owner?

IMO, !nobody should be notified by default. It's better to check the ticket tables of the project regularly, e.g. in team meetings or during their preparation. Anyway, the announcer plugin offers a feature "ticket component subscriptions" in Preferences-->Announcements, and it's a good idea to add "ticket project subscriptions" as well. This way this plugin changes Trac's default behavior a little, only. And it's up to the preferences of a certain project leader whether he must poll for changes or gets notified by automatisms.

[nielo]

Okay, I see. This improvement would be wonderful.