Currently, a number of Flow notification types render differently if they are about the current user's user talk page. In order to be able to treat user-talk-related notifications differently in other ways as well (mark them as urgent, and make them affect the OBOD) we need them to be separate types, e.g. flow-new-topic-usertalk.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Split flow-* and flowusertalk-* notifications | mediawiki/extensions/Flow | master | +285 -189 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T119713 Update Help:Notifications | |||
| Resolved | None | T114351 Better organisation for the Notification System | |||
| Resolved | Catrope | T123018 Revise Sorting of Notifications on the Fly-Out Menus | |||
| Resolved | • KMuthu | T137954 No orange-bar-of-doom when a message is posted on a user talk page using Flow | |||
| Resolved | SBisson | T138220 Make user-talk-related Flow notifications their own types |
Event Timeline
Comment Actions
Change 295484 had a related patch set uploaded (by Sbisson):
[WIP] Split flow-* and flowusertalk-* notifications
Comment Actions
Checked flowusertalk-*
According to https://gerrit.wikimedia.org/r/#/c/295484/
Split flow-* and flowusertalk-* notifications It applies to: - flow-new-topic - flow-description-edited - flow-post-reply - flow-post-edited - flow-topic-renamed - flow-summary-edited - flow-topic-resolved
The above events when they happened on a user talk page have been recorded in db as the following:
flowusertalk-new-topic
flowusertalk-description-edited
flowusertalk-post-reply
flowusertalk-post-edited
flowusertalk-topic-renamed
flowusertalk-summary-edited
flowusertalk-topic-resolved