We are trying to cleanup our user database by making the retired users unsearchable in the assignee field and reporters field. Since some of these users have created issues and dashboards and deleting them is not an option for us.
As previously read, we have already removed the necessary groups and roles the users belong to. However, upon testing, we saw that the issue can still be set to these users as the reporter (when Modify Reporter is on). Please let us know what other configuration needs to be done in order to completely hide these users. Thanks!
Hi Nic,
My fault for the wrong choice of words. The user actually doesn't have any more roles nor in any groups but still appears in the reporters list when modifying a reporter field. The permission scheme was already checked and confirmed that the user doesn't belong to any of the roles or groups so we would to know what else did we miss. We are using JIRA 4.2.3.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, so what exactly do you have in the permission scheme for "create issue"?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We have four customized roles under the create issue permission scheme and the user is not part of any of these roles now.
Project Role (Risk Management Department)
Project Role (General Manager )
Project Role (Division Head)
Project Role (Incident Reporters)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any comment on this problem? Or is this a known bug in JIRA 4.2.1?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Alaine, did you ever find out the answer to this? We are having a similar problem where users are showing up when we modify reporter that do not have Create Issue permissions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sarah, the behavior is still the same even with the latest major version (we are using only 6.1.4 though) I am not sure if this was fixed in the latest minor version
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess this is not answerable? I will then revert to the atlassian support site. Thank you for your help.
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.
Hi Nic,
We only assign user IDs to the roles. We don't assign groups under roles. Since this is individual information, we cannot share it outside of our institution. But I have checked it already and confirmed that the user is not under any of these roles anymore. Any other advice?
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.