We just shipped the Issue Collector bundled with JIRA 5.1, but there's also an updated version available on marketplace.
We specifically targeted a lot of the bug fixes and improvements for the anonymous use case, since the Issue Collector is designed for feedback from users who are not JIRA users.
However, if you put the issue collector on a website outside your corporate network, and your JIRA instance is inside your corporate network (and you don't allow HTTP/S traffic to reach your JIRA instance), then the Issue Collector won't be able to submit feedback to JIRA. I.e. if you can get to JIRA from outside your corporate network without a VPN, then you should be able to use the Issue Collector.
So I doubt it is a JIRA permissions issue, it's likely because JIRA isn't accessible via HTTP or HTTPS. A solution could be to allow traffic from the server that the Issue Collector is embedded in, to your internal JIRA instance, though I realize your network policy might not allow that.
Another option is a second JIRA instance outside your corporate network for external projects. A lot of JIRA customers have internal and external JIRA instances since some information or projects are internal and sensitive, while others are shared with customers, clients, or partners.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.