It gives you an "interesting" situation where a user can create an issue, fill in all the fields, clicks "create" and then lands on a "Permission denied or issue does not exist" screen. The issue is fine, it's worked, but the user creating it can't see it.
This actually does have valid use cases, but for 99.9% of people, the answer should be "make sure the permission scheme entry for "Create issue" is a subset of the entries for "Browse project"
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot