Most module maintainers (and maintainers of other projects) consider any issue in the support request category to never rise to the highest Priority level of critical.

Even if we have hooked up our web server to a mechanical arm, and we believe our configuration of a module has caused the arm to pick up a gun and start firing bullets wildly in our direction, and we would like it to stop— this situation is considered specific to us, and as such a non-critical support issue. Unless we have good reason to believe our problem is due to a bug in the module's code, we should (while dodging bullets) politely mark the priority of our support request no higher than major.

Tasks and feature requests are likewise not typically considered critical, and we should keep our assessment of priority modest, unless we come to understand that a project's developers explicitly are organizing tasks in a certain way.

A critical issue is one which prevents an entire project from working (or that causes a module or theme to take down a site).

[This goes with the general topic how to use and file issues on the issue queue. See also and refer people to Priority levels of issues in the Handbook on d.o.]