nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Reporter to see own issues only

Reatha Ek

Hello - looked for an ansewer but didn't find.

How do I configure JIRA so that reporters need to sign in (so they can be identified automagically) but only see their own requests?

I already set up a new group/role 'jira-reporter', but they can't login as such. I need to make them 'jira-users', but then they see all...

Accepted answers

Nic Brough -Adaptavist-

You need to do two things

1) Stop using Jira-users in your permission schemes. Jira-users should be used to say "this person can log in", not "this person can see project X". Separate your users into groups, put all of them in jira-users, but do not use it anywhere other than "can log in"

2) Enable reporter only flag - it's turned off by default, because if it's used inappropriately, it breaks stuff. Basically, it's off so the admin is forced to put the effort into finding it, and hence sees the warnings.

See http://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission

To use it - enable it in the config, and then change the permission scheme for the project(s) you want to do it in. Take away all the "browse" permissions you don't want (especially the "reporter" permission), and add the new "current reporter only"

All comments

Nic Brough -Adaptavist-

You need to do two things

See http://confluence.atlassian.com/display/JIRA/Current+Reporter+Browse+Project+Permission

MinC

How do I configure JIRA so that reporters need to sign in (so they can be identified automagically) but only see their own requests?

Permission to login to JIRA requires JIRA Users permission in Global Permission. You need to add the new group to JIRA Users permission in Global Permission so that they can login to JIRA.

As for the reporter to see own issues, you may need to create an Issue Security Scheme and add the new group to a security level. By doing this, only specific group can view the specific issue. You can either add the new group or the Reporter.

Beth Schaeferma

To create a support project for an enterprise:

(1) Assign the group Jira-users to whatever role you might have defined as a normal team member of the support project

(2) Create an issue security scheme that allows only the reporter to see his/ her own tickets (see Min Yee's comment above)

(3) Create a support Group (Support Group) of the people who will pick up the tickets and respond. This step is required to limit the names that appear in your Assignee user-picker (so that it isn't everyone in the enterprise)

(4) In the permissions scheme assigned to your support project, add the Support Group as assignable users and remove any other pre-defined groups.

Reatha Ek

Thanks for all your answers - this one works best for us!

The only issue we have is that the reporters can't add any comments to their issues even though the Permission Scheme explicitly permits it... At least I think it does... Any easy transparent safe fix for that?

Nic Brough -Adaptavist-

Jira doesn't have nested groups.

You can put people in many groups though.

Niklas Jonsson1

A short question to you first suggestion about adding all groups in jira-user Nic. When editing the jira-user group in latest 6.1 Jira it seems like I can't add a group in to another group, only users? do I need to turn on nested groups or am I just doing it wrong?