BetterBugSubscriptionsAndNotifications

Summary

Describe in a few phrases the main findings of the testing. If someone read only this part of the report, what would you want them to know?

Findings

Users can filter out notifications generated because of a change they made themselves

• 770267: There is a full-stop (period) at the end of the option text. This is inconsistent with the other options on that page.

• 770387: After changing the configuration option, there is no notification of what change you've made.

Actions that are done and then quickly undone will not generate notification emails

• Feature appears to work as intended.
• I made sure that I had selected the "Send me bug notifications for changes I make." configuration option and then I added a tag of "test-test-test" to bug 770267. Immediately, I removed the tag. I have not received an email.

Subscribe to individual bugs, choosing to filter by events

• "this bug is fixed or re-opened": this gave me pause. The bug I was looking at was open. I didn't understand how it could be re-opened. why would this bug be re-opened? It i's not closed. It seems pretty clear that this means that, should the bug ever be closed, this option would give you an email if were then to be opened again. However, I had to pause to think about what it might mean as it seemed to imply that the bug was currently closed. Could we improve this by saying, "this bug is closed or later re-opened"? Do we really mean "fixed" here and not "closed"?

• 770293: Unsubscribing using the "minus sign" button beside my name on the bug page didn't work. My name disappeared but when I clicked on "Subscribe" I was given the full the subscription options. Also, screen cast attached to bug report.

"mute" their notifications on individual bugs

• 770315: The help pop-up could be clearer and use words that are more familiar to our users.

• I muted bug 674422 on staging, as I was subscribed via a structural sub. It timed out first time round. Second time it worked but took four or five seconds. This was much quicker on production with bug 770293, to which I have a direct subscription.

• 770342: When unmuting a bug, the overlay confusingly talks about subscribing to the bug that I'm already subscribed to.

• 770345: when muting a bug, your name is removed from the subscribers list. When unmuting the same bug, your name is not put back in the subscribers list.

Make filters for structural subscriptions

• 771217: the "Edit bug mail" link appears for projects where I have no existing subscription. This implies there is a subscription and could confuse people.

• 771226: the overlay for creating a new structural subscription is offset to the right.

• 771222: this is almost certainly not a bug in the bug notifications/subscriptions story; I think it's likely to be related to the way feature flags work. While not logged in, I clicked "Subscribe to bug mail", was redirected to the LP login and then directed back to the current live production version of the structural sub page.

• 771231: there is no confirmation after making a structural subscription.

• 771232: the overlay to edit a subscription has the header "Add a mail subscription..."

• 771236: when editing a structural subscription, the recipient is not editable.

• 771239: "Select all" and "Select none" are too close together in the "Importances" and "Statuses" sections of the "Bugs must match this filter" accordion.

• 771247: when editing a subscription, the "are added or changed in any way" option doesn't really give you that unless you also select the "Send mail about comments" check-box.

• 771260: the tags section of the accordion does not tell you how to separate tags, unless you click the help pop-up.

• 771269: the description of which importances and statuses trigger an email are slightly hide to read.

• 771279: no confirmation step when deleting a structural subscription.

• 771282: team subscriptions use "you" in the description of what email will be sent, thereby slightly obscuring the fact that all members of the named team will receive that email.

Recommendations

• Short recommendation that describes the outcome, rather than the implementation detail.

• Consider things that would make testing easier.

• Consider patterns that would result in systematic quality improvements (e.g. fixing 758976)