[wp-meta] [Making WordPress.org] #308: Collapse watching and notifications for ticket creators

[Making WordPress.org]

#308: Collapse watching and notifications for ticket creators
------------------------------+------------------
  Reporter:  danielbachhuber  |      Owner:
      Type:  defect           |     Status:  new
  Priority:  normal           |  Component:  Trac
Resolution:                   |   Keywords:
------------------------------+------------------

Comment (by nacin):

 I agonized over how notifications should work for a while. It was designed
 to have three states, all in one:
  * receiving notifications for a ticket due to properties (milestone,
 component, focus, reporter, owner, participant)
  * explicitly watching a ticket, thus adding it to your favorites, and
 always receiving notifications, even if the corresponding property changes
  * explicitly blocking the implicit notifications

 So yeah, it's possible to actually be a reporter and block notifications
 to one of your tickets. At first this sounds odd, but at the same time,
 sometime tickets go way beyond the reporter and turn into monster tickets.
 Think https://code.google.com/p/chromium/issues/detail?id=236298 or plenty
 of tickets on core trac.

 I agree that it's a bit odd that a reporter isn't already "Watching" a
 ticket upon creation. A reporter change doesn't happen in practice, so
 they don't need to worry about a property change causing them to no longer
 be watching their ticket. But maybe it's the wording. Maybe if you're
 implicitly receiving notifications, "Watch this ticket" should simply read
 "Star this ticket" or "Favorite this ticket".

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/308#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org