What the best (correct) way to hide a project and still (new) users being able to mail to it..
Currently,the new users are becomming members of "jira-users".
Some projects have a permission scheme with "Browse Projects" and "Create Issues" permissions assigned to "jira-users", so all new users (being created) can create an Issue into them.
If I remove "Browse Projects", the "Create Issues" is not enough to create the issue, this fails.
Since ALL users have (at least) "jira-users" membership, they can see many projects, but no issues in them (due to Security Level)
So it is possible to create a project that is "hidden", but still, new users can be created and an issue from the mail.
It seems this wont be possible, as the workaround for this should be enabling both Browse Projects and Create Issue to enable user to create issue in the instance, and setting up a post function to set the issue security level so that the issue in the project can't be seen by normal user (basically hiding the issue but not the project it self).
What objective are you trying achieve here by hiding the project? Can you further elaborate on that?
Currently, when a customer logs in, he can se the existence of another Customers project, due to that "jira-users" have "Browse Project" rights on it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.