Hiram confirmed this is possible.
Jaime.....as I understand it, it's all or nothing at the moment, but I believe with some dev. effort on the Forge, we could change it to be done on a per-project basis. Hiram, can you comment?
From: Jaime Meritt
Sent: 14 July 2009 13:02
To: Amanda Hall
Subject: Re: Who should have access to create jira issues for Forge projects
Thanks for the reminder, must have missed this one. During the fuse forge planning this question came up and the decision was that it would be the decision of the project owner whether they wanted to accept non-member jiras for their project. Sounds like this was never implemented. Can we make it a project level acl or do we have to do it all or nothing?
From: email@example.com firstname.lastname@example.org On Behalf Of Amanda Hall
Sent: 02 July 2009 12:16
To: Jaime Meritt
Subject: Who should have access to create jira issues for Forge projects
An Actional Diagnostics customer contacted me earlier this week to let me know that he couldn't raise some issues in jira that he had found with the product. James, Hiram & I discussed this briefly on the #Forge channel  and it seems the current setup doesn't allow anyone other than internal folks(dev & support) to raise issues in jira for our Forge projects. As you'll see from the discussion there are pros and cons to allowing fusesource subscribers to raise issues themselves, the main pro being it encourages participation from customers and helps build the community and the main con being the potential for jira to become polluted with junk.
It's easy for us to change, but we'd like to get your feedback first as to what your expectation is around jira usage for participants/customers on Forge projects.