"Import Issues" function should have additional permission requirements

The ability introduced in JIRA 6.2.x to allow users (not just admins) to import from .CSV files really needs some other limiting factor beyond "Create Issue" project permission and "Bulk Edit" global permission. Importing is not the same as bulk editing.

Importing via .CSV can easily go wrong spawning tons of errors, especially for those who have little experience formatting them. This can cause all types of problems throughout the entire JIRA instance. And while most users would like the ability to import issues as it is an easier way for them to enter issues, most either will not take the time to correctly format their import, read how to do so or pre-test the import before they do so. This can be very, very bad.

So personally, as my companies system administrator, I have to make the choice of taking the risk to allow them this function (since they require the "Create Issue" ability in their own projects and they use Bulk Editing, turn off bulk editing which they have used for 2 1/2 years, or not upgrade above the 6.1.x series. At present, only the latter is a viable solution.

Please add additional abilities for system administrators to limit the use of bulk importing (like it's own global permission setting)