Opened 10 years ago

Closed 4 years ago

#308 closed defect (bug) (worksforme)

Collapse watching and notifications for ticket creators

Reported by: danielbachhuber's profile danielbachhuber Owned by:
Milestone: Priority: low
Component: Trac Keywords:


When I just created a ticket, this was an unexpected result:

I expected that "watching" and "notifications" are one and the same — when I create a new ticket, I'm watching the ticket by default. If I don't want the notifications, I can unwatch the ticket.

Change History (5)

#1 @nacin
10 years ago

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 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".

#2 @danielbachhuber
10 years ago

So yeah, it's possible to actually be a reporter and block notifications to one of your tickets.

In my simpleton mind, this could be achievable by auto-starring any tickets you open. If you want to unsubscribe, you unstar the ticket.

Similarly, following a component, milestone, etc. means you'll be auto-starred for any new tickets. Unfollow to unstar.

But, as I've described means less control to the user — favoriting means getting email notifications and getting email notifications means favoriting. I do understand the desire to potentially favorite a subset of those tickets you get email notifications for.

With this in mind, I think I'd still encourage the act of creating a ticket to automatically favorite that ticket. It seems implied that if you create a ticket, it will be one of your favorites.

It would probably also be nice to have a canonical page somewhere for how all of the notification behavior works. I suspect this is it:

#3 @samuelsidler
8 years ago

  • Priority changed from normal to low

This ticket was mentioned in Slack in #meta by obenland. View the logs.

6 years ago

#5 @dd32
4 years ago

  • Resolution set to worksforme
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.