Change Details

This task is about deciding on and implementing the logic for how topic subscription notifications will get "bundled" /"grouped" within Echo's notice drawer/tray [i] === Requirements //In progress...// As someone who is subscribed to a discussion in which many new comments are being posted within a "short" time period: 1. I want to be able to see notifications for those comments en masse, so they do not overwhelm other notifications and cause me to miss notifications about other activity. 2. I want the notifications for these comments to be grouped in such a way that I feel confident taking an action (e.g. marking them as read, visiting the discussion to which these comments have been posted) on that bundle. 3. I want to be able to triage those notifications (e.g. mark them as read) en masse, so that I don't need to spend unnecessary time and effort taking the same action, with the same impact, multiple times. === Open questions - [ ] 1. What are the criteria for when notifications are bundled together? In other words, what does the bundle string look like? - [ ] 2. What text is shown for bundled notifications? This is usually different from a normal notification, e.g. "3 people thanked you for your edit on XYZ" instead of "Ed thanked you for your edit on XYZ", and usually focuses on what the bundled notifications have in common - [ ] 3. What text is shown for the individual notifications in a bundle? This usually focuses on what is different, e.g. "Ed thanked you", "Jess thanked you" - [ ] 4. When the user clicks the bundle, where should they go? Clicking the "Expand" link expands the bundle, but clicking elsewhere usually takes you somewhere. Typically this is to the thing that the notifications have in common. For example, clicking a single notification that says "Ed posted on your user talk page" would take you to Ed's post, but clicking a bundle that says "3 people posted on your user talk page" would just take you to your user talk page, but not to a specific post/section //Thank you to @Catrope for sharing the above questions with the #editing-team and helping us to understand, more broadly, how notifcation grouping/bundling works in Echo.// --- |i. Echo's notice drawer/tray |--- |{F34124547} |//source: [File:Screenshot_of_Echo_notification_extension](https://www.mediawiki.org/wiki/Extension:Echo#/media/File:Screenshot_of_Echo_notification_extension.png)//

This task is about deciding on and implementing the logic for how topic subscription notifications will get "bundled" /"grouped" within Echo's notice drawer/tray [i] === Stories //In progress...// As someone who is subscribed to a discussion in which many new comments are being posted within a "short" time period: 1. I want to be able to see notifications for those comments en masse, so they do not overwhelm other notifications and cause me to miss notifications about other activity. 2. I want the notifications for these comments to be grouped in such a way that I feel confident taking an action (e.g. marking them as read, visiting the discussion to which these comments have been posted) on that bundle. 3. I want to be able to triage those notifications (e.g. mark them as read) en masse, so that I don't need to spend unnecessary time and effort taking the same action, with the same impact, multiple times. === Requirements //Requirements will be populated once the `Open questions` below have been answered.// === Open questions - [ ] 1. What are the criteria for when notifications are bundled together? In other words, what does the bundle string look like? - [ ] 2. What text is shown for bundled notifications? This is usually different from a normal notification, e.g. "3 people thanked you for your edit on XYZ" instead of "Ed thanked you for your edit on XYZ", and usually focuses on what the bundled notifications have in common - [ ] 3. What text is shown for the individual notifications in a bundle? This usually focuses on what is different, e.g. "Ed thanked you", "Jess thanked you" - [ ] 4. When the user clicks the bundle, where should they go? Clicking the "Expand" link expands the bundle, but clicking elsewhere usually takes you somewhere. Typically this is to the thing that the notifications have in common. For example, clicking a single notification that says "Ed posted on your user talk page" would take you to Ed's post, but clicking a bundle that says "3 people posted on your user talk page" would just take you to your user talk page, but not to a specific post/section //Thank you to @Catrope for sharing the above questions with the #editing-team and helping us to understand, more broadly, how notifcation grouping/bundling works in Echo.// === Done - [ ] All `Open questions` have been answered - [ ] The `Requirements` have been implemented --- |i. Echo's notice drawer/tray |--- |{F34124547} |//source: [File:Screenshot_of_Echo_notification_extension](https://www.mediawiki.org/wiki/Extension:Echo#/media/File:Screenshot_of_Echo_notification_extension.png)//

This task is about deciding on and implementing the logic for how topic subscription notifications will get "bundled" /"grouped" within Echo's notice drawer/tray [i] === RequirementsStories //In progress...// As someone who is subscribed to a discussion in which many new comments are being posted within a "short" time period: 1. I want to be able to see notifications for those comments en masse, so they do not overwhelm other notifications and cause me to miss notifications about other activity. 2. I want the notifications for these comments to be grouped in such a way that I feel confident taking an action (e.g. marking them as read, visiting the discussion to which these comments have been posted) on that bundle. 3. I want to be able to triage those notifications (e.g. mark them as read) en masse, so that I don't need to spend unnecessary time and effort taking the same action, with the same impact, multiple times. === Requirements //Requirements will be populated once the `Open questions` below have been answered.// === Open questions - [ ] 1. What are the criteria for when notifications are bundled together? In other words, what does the bundle string look like? - [ ] 2. What text is shown for bundled notifications? This is usually different from a normal notification, e.g. "3 people thanked you for your edit on XYZ" instead of "Ed thanked you for your edit on XYZ", and usually focuses on what the bundled notifications have in common - [ ] 3. What text is shown for the individual notifications in a bundle? This usually focuses on what is different, e.g. "Ed thanked you", "Jess thanked you" - [ ] 4. When the user clicks the bundle, where should they go? Clicking the "Expand" link expands the bundle, but clicking elsewhere usually takes you somewhere. Typically this is to the thing that the notifications have in common. For example, clicking a single notification that says "Ed posted on your user talk page" would take you to Ed's post, but clicking a bundle that says "3 people posted on your user talk page" would just take you to your user talk page, but not to a specific post/section //Thank you to @Catrope for sharing the above questions with the #editing-team and helping us to understand, more broadly, how notifcation grouping/bundling works in Echo.// === Done - [ ] All `Open questions` have been answered - [ ] The `Requirements` have been implemented --- |i. Echo's notice drawer/tray |--- |{F34124547} |//source: [File:Screenshot_of_Echo_notification_extension](https://www.mediawiki.org/wiki/Extension:Echo#/media/File:Screenshot_of_Echo_notification_extension.png)//