Some JIRA installations have a use-case where they want a user to only see projects they can report issues in. Normally when you add the "Current Reporter" group to the "Browse Project" permission of one project, this project instantly becomes visible to all users (via the project table portlet), even if they are unable to report an issue in that project or not.

This guide is for those who want a user to only see issues they've reported and also not see any projects that's irrelevant to them (they are unable to create issues for). This permission is available as an optional permission type (since JIRA 3.2). You will need to uncomment the lines below in the file the WEB-INF/classes/permission-types.xml. Restart JIRA and this type will be available in your standard permissions page.

If you're running a WAR deployment, you'll need to rebuild the WAR after the change and redeploy. You may need to remove your old exploded WAR directory for the new one to take effect.

<type id="reportercreate" enterprise="true">

When using this special permission, users will only see projects where thy have create permission to and issues within that project where they are the reporter.

This permission is deliberately commented out of the permission-types.xml file. This is to ensure that only advanced JIRA administrators are able to access it. There are two reasons behind this:

  • Firstly, the permission itself is used in fairly sophisticated scenarios.
  • Secondly, the implementation of this permission is potentially dangerous. For example, it is possible to put your JIRA instance in an infinite loop by mapping this permission to the Create Issue function.