View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002312 | Composr | core_notifications | public | 2016-03-18 04:17 | 2022-08-15 17:10 |
| Reporter | Patrick Schmalstig | Assigned To | Patrick Schmalstig | ||
| Severity | Feature-request | ||||
| Status | resolved | Resolution | no change required | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0002312: Web notification marking as read not efficient | ||||
| Description | There are several instances where clicking on a web notification doesn't mark it as read like it should. For example, clicking on a notification about a reply on a forum doesn't typically mark that notification as read. Clicking on a periodic content review web notification doesn't mark it as read until you actually do something, like edit that content. I personally think web notifications are "read" after a user sees them (individually, not via. the 5-notification popup), even if the user didn't specifically click the link in the notification or do something regarding it. | ||||
| Tags | No tags attached. | ||||
| Time estimation (hours) | 0.75 | ||||
| Sponsorship open | |||||
|
|
Topic notifications are meant to mark read, as a special case. I think with output streaming on it wasn't working right, so that will be fixed. However, in the general case, it's not expected for notifications to automatically mark as read, as that wasn't implemented as one of the features. I'll therefore leave this topic open for possible future improvements. |
|
|
I have output streaming disabled currently on b4 and the problem seems to remain. So what was the original Composr plan? In other words what would constitute as a "read" notification? |
|
|
"I have output streaming disabled currently on b4 and the problem seems to remain. " - you're right. Almost fixed now. Was a block caching issue. "So what was the original Composr plan? In other words what would constitute as a "read" notification?" - apart from topics, you need to mark them read via the link. I agree with your comments, just it hasn't been done initially and I didn't honestly think of it. |
|
|
This issue is hard to follow, but as I understand it - we are saying that when you click on a notification to view it (or is it there is a URL attached to it?), it should mark that notification read. Rather than you needing to explicitly click a button to mark notifications read. |
|
|
Patrick had a look and could no longer find an issue. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-03-18 04:17 | Patrick Schmalstig | New Issue | |
| 2016-03-21 21:58 | Chris Graham | Summary | Composr 10b4: Web notification marking as read not efficient => Web notification marking as read not efficient |
| 2016-03-21 22:05 | Chris Graham | Note Added: 0003454 | |
| 2016-03-22 06:15 | Patrick Schmalstig | Note Added: 0003472 | |
| 2016-03-23 01:04 | Chris Graham | Note Added: 0003482 | |
| 2016-04-15 14:03 | Chris Graham | Time estimation (hours) | => 0.75 |
| 2019-06-27 18:51 | Chris Graham | Tag Attached: Roadmap: v12 | |
| 2020-03-28 00:57 | Chris Graham | Severity | @40@ => Feature-request |
| 2021-07-23 22:31 | Chris Graham | Note Added: 0007110 | |
| 2021-07-23 22:32 | Chris Graham | Assigned To | => Patrick Schmalstig |
| 2021-07-23 22:32 | Chris Graham | Status | non-assigned => assigned |
| 2021-07-24 15:20 | Chris Graham | Status | assigned => closed |
| 2021-07-24 15:20 | Chris Graham | Resolution | open => no change required |
| 2021-07-24 15:20 | Chris Graham | Note Added: 0007111 | |
| 2022-08-15 17:10 | Chris Graham | Status | closed => resolved |
| 2022-08-15 17:10 | Chris Graham | Tag Detached: Roadmap: v12 |
