I am trying to set up a permission scheme for my project so that any users within a particular project role can create tickets, but individual users can only view tickets that they have created. I tried to set this up by giving "Create Issues" permission to the project role, then giving "Browse Projects" permission to "Reporter" and this worked but also has unintended impacts. Now all users in the system (including those not in this particular project) are able to view this project under the "Projects" tab through Browse Projects. They can't view any issues in the project since they are not the reporter, and they can't create issues since they dont have the permission, but they can nevertheless see the project including the client name which creates confidentiality concerns. Is there any way to set project permissions so only reporters within a particular group can view tickets they've created in the project?
I don't have access to change the code (per option 2), so do you understand what he meant by option 1?
"You can use "issue security" to do this, creating a scheme that says "reporter" and then defaults, but that allows users to remove the security and it's a bit fiddly."
Actually, I don't think that option 1 really relates to this exactly problem - this is issue security, while we need project's pemissions limitations. So - only uncommenting one block in config file could help.
Maybe I'm wrong about option 1 (I'm definetily not a Jira spetialist) and Nic would answer you on that thread...
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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