Bugzilla

After discussion with wise wada, the following clarifies comment 0, in particular the meaning of "especially relevant"...

The goal here is not to encompass *all* bugs of interest to enterprises, because that is literally thousands of bugs from a huge range of functionality, some of which impact a tiny number of enterprises. Rather, the goal here is to identify "high value" bugs, i.e. "key bugs", so that enterprise users can track the progress and addition of these bugs via this single meta bug, and with a minimum amount of (bug)mail. 

So until modified, please use a severe, narrow definition in choosing bugs to blocks this bug, and we can relax the definition later if needed. These points may help define this narrow perspective:

* We avoid listing large numbers of bugs that are otherwise easily queriable or identifiable using bugzilla. So for example we would generally not list all bugs from the import and migration components, bugs with "exchange" in the summary, etc. But we might pick very special, very few bugs out of that class that meet some of the criteria listed below.
* The bug is _not_ of equally high impact to the average user that is outside the enterprise, because by definition such a bug is high value to everyone and is therefore already important in its own right (i.e. bugs should have unique impact in the enterprise) 
* The bug should be "high value" in the sense that it provides significant return in user productivity, pain reduction or improvement in product management.
* The bug should impact a non-trivial percentage of enterprises as best as one can evaluate or guess (use your own good judgment of what constitutes non-trivial, but the minimum definition is the numbers affected should well exceed your own institution)

So, bugs that might block:
* the bug significantly affects mail server load
* the bug significantly impacts networked resources (as a recent example)
* special bugs that involve preferences, installation, software update, deployment ... including those from non-Thunderbird bugzilla product categories, like Core and Toolkit 

Note, there are other ways to impact bugs that to not fit the above criteria and therefore not block this bug, but that are important to you and your institution :
* discuss your issues, and help others in tb-enterprise [1] and other appropriate forums
* help triage or fix bugs (or find some people in your organization who can)
* organize meta bugs or making new ones (queries below [2]) so that bugs are more easily evaluated and more quickly addressed at a high level 
* file well defined, well researched bugs

[1] https://wiki.mozilla.org/Thunderbird/Enterprise
[2] Meta bugs
* Thunderbird and Mailnews meta bugs (~90 bugs) https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=anywordssubstr&keywords=meta&keywords_type=allwords&field0-0-0=short_desc&resolution=---&classification=Client%20Software&classification=Components&query_format=advanced&type0-0-0=nowords&value0-0-0=count%20counts&field1-0-0=short_desc&product=MailNews%20Core&product=Thunderbird 
* Toolkit and Core meta bugs (~450 bugs) https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=anywordssubstr&keywords=meta&keywords_type=allwords&field0-0-0=short_desc&resolution=---&classification=Client%20Software&classification=Components&query_format=advanced&type0-0-0=nowords&value0-0-0=count%20counts&field1-0-0=short_desc&product=Core&product=Toolkit

After discussion with wise wada, the following clarifies comment 0, in particular the meaning of "especially relevant"...

The goal here is not to encompass *all* bugs of interest to enterprises, because that is literally thousands of bugs from a huge range of functionality, some of which impact a tiny number of enterprises. Rather, the goal here is to identify "high value" bugs, i.e. "key bugs", so that enterprise users can track the progress and addition of these bugs via this single meta bug, and with a minimum amount of (bug)mail. 

So until modified, please use a severe, narrow definition in choosing bugs to blocks this bug, and we can relax the definition later if needed. These points may help define this narrow perspective:
 1) We avoid listing large numbers of bugs that are otherwise easily queriable or identifiable using bugzilla. So for example we would generally not list all bugs from the import and migration components, bugs with "exchange" in the summary, etc. But we might pick very special, very few bugs out of that class that meet some of the criteria listed below.
 2) The bug is _not_ of equally high impact to the average user that is outside the enterprise, because by definition such a bug is high value to everyone and is therefore already important in its own right (i.e. bugs should have unique impact in the enterprise) 
 3) The bug should be "high value" in the sense that it provides significant return in user productivity, pain reduction or improvement in product management.
 4) The bug should impact a non-trivial percentage of enterprises as best as one can evaluate or guess (use your own good judgment of what constitutes non-trivial, but the minimum definition is the numbers affected should well exceed your own institution)

So, bugs that might block:
5) the bug significantly affects mail server load
6) the bug significantly impacts networked resources (as a recent example)
7) special bugs that involve preferences, installation, software update, deployment ... including those from non-Thunderbird bugzilla product categories, like Core and Toolkit 

Note, there are other ways to impact bugs that to not fit the above criteria and therefore not block this bug, but that are important to you and your institution :
8) discuss your issues, and help others in tb-enterprise [1] and other appropriate forums
9) help triage or fix bugs (or find some people in your organization who can)
10) organize meta bugs or making new ones (queries below [2]) so that bugs are more easily evaluated and more quickly addressed at a high level 
11) file well defined, well researched bugs

[1] https://wiki.mozilla.org/Thunderbird/Enterprise
[2] Meta bugs
* Thunderbird and Mailnews meta bugs (~90 bugs) https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=anywordssubstr&keywords=meta&keywords_type=allwords&field0-0-0=short_desc&resolution=---&classification=Client%20Software&classification=Components&query_format=advanced&type0-0-0=nowords&value0-0-0=count%20counts&field1-0-0=short_desc&product=MailNews%20Core&product=Thunderbird 
* Toolkit and Core meta bugs (~450 bugs) https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=anywordssubstr&keywords=meta&keywords_type=allwords&field0-0-0=short_desc&resolution=---&classification=Client%20Software&classification=Components&query_format=advanced&type0-0-0=nowords&value0-0-0=count%20counts&field1-0-0=short_desc&product=Core&product=Toolkit