How to customise JIRA Core so reporters only see issues they reported
The information in this page relates to customisations in JIRA. Consequently, Atlassian Support cannot guarantee to provide any support for the steps described on this page as customisations are not covered under Atlassian Support Offerings. Please be aware that this material is provided for your information only and that you use it at your own risk.
Also, please be aware that customisations done by directly modifying files are not included in the upgrade process. These modifications will need to be reapplied manually on the upgraded instance.
プラットフォームについて: Server と Data Center のみ - この記事は、サーバーおよびデータセンター プラットフォームのアトラシアン製品にのみ適用されます。
Some JIRA Core configurations 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 can also be configured in JIRA Service Desk as per Getting started with Jira Service Desk and is now the recommended method of doing this.
$JIRA_INSTALL/atlassian-jira/WEB-INF/classes/permission-types.xmlto uncomment the below XML:
<!-- <type id="reportercreate" enterprise="true"> <class>com.atlassian.jira.security.type.CurrentReporterHasCreatePermission</class> </type> -->
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.
You should see the Reporter (show only projects with create permission) option added to the Add New Permission page (Managing project permissions), as per the screenshot below.
This is different to the original Reporter permission.
This permission is deliberately commented out of the
permission-types.xml file to ensure that only advanced JIRA administrators are able to access it. There are two reasons behind this:
- The permission itself is used in fairly sophisticated scenarios.
- 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.