[MacPorts] #52107: Trac: options to temporarily disable emails on tickets that affect many maintainers and commits

[MacPorts]

#52107: Trac: options to temporarily disable emails on tickets that affect many
maintainers and commits
-----------------------------+----------------------
  Reporter:  mojca           |      Owner:  admin@…
      Type:  enhancement     |     Status:  assigned
  Priority:  Low             |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+----------------------
Description changed by mojca:

Old description:

> I opened this to discuss options/ideas to allow "quiet" changes on
> tickets like #39383 or #48365/#52081.
>
> Some solutions that come to my mind:
>
> * having a separate field similar to descriptions that would not generate
> email traffic
> * having a checkbox saying "don't send an email when I add these changes"
> * being able to a reply with a checkbox "anyone can edit text of this
> reply" (people could then edit reply without generating more email
> traffic)
> * open 100 new tickets and only display a ticket query in the master
> ticket (I don't like that idea too much though)
> * open two tickets, one to notify developers, the other one without any
> subscribers to actually track the progress (ideally I would like to have
> the ability to include the whole description field from another ticket)
>
> See also https://trac-hacks.org/wiki/QuietPlugin for a potentially useful
> plugin.
>
> [https://trac.edgewall.org/ticket/2073#comment:33 Citing]:
>
> > I think it could be good to take the discussion of your use case over
> to the trac-users MailingList. I have ideas on how to solve your issue,
> and would be happy to commit some time to implementing a plugin (if
> needed), for such a big and important open source project that uses Trac
> ;)
> >
> > If you start a thread on trac-users with your ideas on how to solve it
> we can start discussing potential solutions.

New description:

 I opened this to discuss options/ideas to allow "quiet" changes on tickets
 like #39383 or #48365/#52081.

 Some solutions that come to my mind:

 * having a separate field similar to descriptions that would not generate
 email traffic
 * having a checkbox saying "don't send an email when I add these changes"
 * being able to a reply with a checkbox "anyone can edit text of this
 reply" (people could then edit reply without generating more email
 traffic)
 * open 100 new tickets and only display a ticket query in the master
 ticket (I don't like that idea too much though)
 * open two tickets, one to notify developers, the other one without any
 subscribers to actually track the progress (ideally I would like to have
 the ability to include the whole description field from another ticket)

 See also https://trac-hacks.org/wiki/QuietPlugin for a potentially useful
 plugin.

 After we started automatically adding new commit messages at the end of
 the tickets, this will become an even bigger problem. Ticket #47197 is
 another example with 60 subscribers and over 200 required commits. On the
 other hand this might be an opportunity to add some more clever
 automatism. My wish would be to have one comment field with a well-defined
 template reserved for the "bot" and then the bot could potentially change
 that comment as new commits arrive.

 We could have some syntax like
 {{{
 Closes: https://trac.macports.org/ticket/{nnnnn} for {portname}
 }}}
 and then the bot could track progress for us in that template.

 [https://trac.edgewall.org/ticket/2073#comment:33 Citing]:

 > I think it could be good to take the discussion of your use case over to
 the trac-users MailingList. I have ideas on how to solve your issue, and
 would be happy to commit some time to implementing a plugin (if needed),
 for such a big and important open source project that uses Trac ;)
 >
 > If you start a thread on trac-users with your ideas on how to solve it
 we can start discussing potential solutions.

--

--
Ticket URL: <https://trac.macports.org/ticket/52107#comment:7>
MacPorts <https://www.macports.org/>
Ports system for macOS