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"
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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