Page MenuHomePhabricator

Squash TicketWatcher and TopicWatcher models
Closed, ResolvedPublic


Currently, we have two models that are watchable (Ticket and Topic). Who watches what is stored in TicketWatcher/TopicWatcher models.

For easier extending of notifications to other objects (like Grants or even whole objects) having single Watcher model (with "type" attribute) would be useful, so making an object watchable wouldn't mean to add new database tables.

This should include a data migration to migrate data from TicketWatcher and TopicWatcher to the new model.

Event Timeline

Urbanecm renamed this task from Squash TicketWatcher and TopicWatcher classes to Squash TicketWatcher and TopicWatcher models.Nov 12 2018, 9:04 AM
Urbanecm triaged this task as Low priority.
Urbanecm updated the task description. (Show Details)
Urbanecm moved this task from Backlog to GCI on the User-Urbanecm board.
Urbanecm moved this task from Inbox to GCI on the WMCZ-Tracker board.

Change 473277 had a related patch set uploaded (by Arcayn; owner: Arcayn):
[wikimedia-cz/tracker@master] Squash Watcher classes into single class

Change 473277 merged by jenkins-bot:
[wikimedia-cz/tracker@master] Squash Watcher classes into single class