Notification Improvements — Fix High-Priority Bugs

🎯 The objective

While we will likely find a large-scale refactor of notifications necessary to bring the features and fixes users want, there are a few bugs that are large enough to demand immediate attention and should be fixed before starting a much larger project. These also include bugs that are regressions, introduced in more recent updates, as well as even longstanding bugs that are causing a dramatic decrease in our rating on Google Play.

🎒 Resources

• [github.com/thunderbird/thunderbird-support-reports/blob/main/lisa/2026/april.md#top-3-friction-points](http://github.com/thunderbird/thunderbird-support-reports/blob/main/lisa/2026/april.md#top-3-friction-points)

🦮 Rules of the Road

ℹ️ Initial definition of requirements and limitations, the scope of this feature and other potential considerations in order to keep the project narrow and focused.

🟢 In Scope

• Bugs that can be fixed quickly
• Bugs that users are having an exceptionally hard time with

🔴 Out of Scope

• Large bugs or structural issues that will require a larger refactor

🚧 Technical and/or Business Requirements

• We’ll need to list and scope out complaints that came to us via Google Play reviews and issues submitted to GitHub