Current Reporter Browse Project Permission

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 are irrelevant to them (i.e. where they are unable to create issues). 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 Installation Folder/atlassian-jira/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.

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

Why isn't this included in JIRA by default?

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.

After uncommenting the lines, start up JIRA again, and you should see the "Reporter (show only projects with create permission)" option added to the Add New Permission page:

Note that this is different than the original "Reporter" permission.

Was this helpful?

Thanks for your feedback!

9 Archived comments

  1. User avatar


    Totally confusing docs.

    24 Sep 2012
    1. User avatar


      this really is.. agreed...

      20 Dec 2012
  2. User avatar


    When i'm using Group Custom Field value have the same issue, but this solution didn't help in this situation. Can  someone advise on this? Thank you in advance.


    25 Oct 2012
    1. User avatar


      Hi. Did you solve this? I am sitting with the same problem

      21 Oct 2013
  3. User avatar



    Can anyone help on how to get this field to appear on my JIRA version 1.6.0_26. I don't have access to the code on my version of JIRA as its a SAAS.

    Any help would be much appreciated.

    07 Mar 2013
  4. User avatar

    Sathish reddy

    How to provide browse permission  on particular tickets   to the users , if they are involved in any work flow changes on the particular tickets ?

    13 May 2013
  5. User avatar

    Fernando Claros

    We finally were able to activate it and it's working fine. 

    The problem now is that our report-only users can see our versions, and they shouldn't. 

    Does anyone know how could we remove their ability to see our versions?


    16 Oct 2013
  6. User avatar

    Erik Saline [BlackPearl PDM]

    I was unaware that adding the Reporter allowed access to all users, is there anyway to add a warning description on the Permissions page next to the Reporter radio button?


    (warning)Adding Reporter to the browser permission will automatically grant all JIRA users permission to view this project.

    09 Jan 2014
  7. User avatar

    Ben Strackany

    I would like to add that this is not documented terribly well.

    Thanks for adding this functionality. Our company does contract software development and we have a need to let certain external users report issues but not see any other issues or projects other than the issues they create and projects we allow them to see. Definitely a bit tricky to understand and implement but so far so good.

    Basically what I did was define Project Roles that would work for any project we work on and associated all of those roles with the various permissions I wanted to allow/disallow. I created a Role called "External User" and applied it to all permissions I wanted to allow those users EXCEPT the Browse Project permission. I then added the reporter/assignee "show only projects ..." to the Browse Projects permission.
    Now when defining a new project I can dictate individual users or groups of users that I would like to be walled off using the "External User" Project Role that I've created. 

    03 Mar 2015
Powered by Confluence and Scroll Viewport