I'm tempted to call this major because it misses an important use case of Jenkins, which is to understand when problems are corrected. A variety of negative things worth tracking can cause a build status to transition to unstable, which the plugin alerts about just fine, but you also want to know when those negative things are corrected, which this plugin does not do unless you track every success event. Would you consider aligning this plugin more closely with Jenkins status changes in other plugins, e.g. email-ext (https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin)? Email-ext treats the status changes:
unstable -> success
failure -> success
The same way with the "fixed" trigger. I'm not arguing to add another trigger condition to the Office 365 Connector plugin, but just to including UNSTABLE -> SUCCESS status changes to the "Notify Back To Normal" event. Currently only FAILURE -> SUCCESS causes "Notify Back To Normal", which doesn't align well with our use case. When developers generate unstable builds from checking in failing tests or adding code analysis errors, we'd like to know when they've fixed it the same we'd like to know when a build recovers from a total failure. If this was done we could rely more on this plugin to post messages to our collaboration systems instead of using email, which we'd absolutely love to do. Thanks!!