Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hi,
when editing an issue and the Reporter field appears I want to know what users are shown in that list.
Is there a filter on users or all users from the system?
Is there a way I can restrict that list?
thanks
This issue is also with Service Desk customers where they can be set as reporter even in non service desk projects. Is there a way to restrict this ?
I can't find a way to stop this.
As it relates to the reporter field, Project A agent can see customers from Project B, there is zero use case for this (if you're moving a ticket from one Project to another where an existing reporter doesn't exist, just let it fail condition and not move).
Interestingly, Request participant behaves as expected (only showing customers from that project).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Anyone who has the permission to create issues in that project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
hmm... ok... but If I have the permission to modify the reporter I can set as reporter users without the Create Permission. Is this correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, it's valid reporters.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hmm... I am running JIRA 7.1.9... I have defined a single user with Create Permission. When I create a ticket I can setup as Reporter other users who DO NOT HAVE the Create Issue Permission.
Is this a bug or normal behavior?
thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
mmm, not sure, it's been a while since I looked at this and it may well have changed. I wouldn't be surprised if the implementation is to allow any active user to be set, as there are cases where it's a valid thing to do.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
is this somewhere stated in the documentation? Can you please confirm that this is actually the case?
a valid case would be: I move an issue from project A to project B and the reporter of the issue does not have the Create Issue permission in project B.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
JIRA does allow you to move an issue from a project and keep the reporter, who is not a valid reporter in the new project. Same thing with assignee. More info at https://jira.atlassian.com/browse/JRA-34148 about why this allowed
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
so the answer to my question as to whom is shown in the reporter field is: any user from the user base!
is this correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I know its been a while, but it really looks like complete active user base is shown in reporter field.
Is really noone bothered with that? We have big teams and in some cases we don't want to have external users shown to all. Is there a way to limit/filter the reporter field?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's the same answer as given 2 years ago - check the permissions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have the same issue and concern - we dont want to have the complete user base, including external users, shown to all users. We looked at the Global Permissions and it is not really helping in restricting access - unless we misinterpret the permissions.
The way we see it, is, that the global permission should be able to let us disable groups from seeing ALL groups and users in the system. Or to allow us to disable external users to be shown -
We can set the external users to be inactive, but that is not really not ideal.
Question remains - Is there a way to limit/filter the reporter field - has anyone found a solution to this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Who has "create issue" permission in the project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I checked the "create issue" permission and removed every role apart from the administrators and still, the external users are showing in the select list for the "reporter"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the same issue:
A service desk team member of project A can select a member of project B even though the member of project B has no create issue permission for project A (double checked via permission helper).
This is a huge issue for us. Is there no way to restrict this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.