Couldn't you just use a single security level and add the reporter and lets say the project role "Users / or members". Then you could make the security level the default level in which case users wouldn't have to set the security level manually?
You need to review the permission scheme for the project.
Specifically, look at the line that says "browse project" - this will give you the rule for who can see the issues in the project. It will be something like "role (users) and role (developers) and group (jira-developers)". You can then look in the groups and roles to see who has access currently.
I suspect you want a simple rule in there like "role (users)" to cover "member of project", but "creator" is a bit more complex.
The mistake most people make at this point is assuming that giving "browse: reporter" will stop anyone other than the reporter seeing their issues, but it's wrong. If you give "browse: reporter", it will give everyone with "create issue" rights a full view of the issues.
There are two ways to do this:
The messy complicated way that needs a bit of code to make it infallible: Set up an issue security scheme that says "reporter can see this issue". If you do this, you're relying on the users to set the right security level, which may be ok, but a lot of people then add code in the workflow to set it automatically, so they don't rely on the users!
The cleaner better option is to enable "reporter browse" permissions. This requires you to change a setting file in your install, and understand that as an admin, you must be careful not to misuse it, but it works.
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