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?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs