How to delete a user which stil has issue assign and reported?

[Philipp Schmidt]

I have severall old users, which need to be deletet. They have issues assigned and reported to. The actual directory is an JiraDirectory. The user left our company and need to be removed.

is it somehow possible to bulk move these issues to some other user?

[Philipp Schmidt]

Now i resettet my ad password and it looks like this might be the solution. Now i have to reset from all users the AD password. this shouldnt be the right solution but it works for us now.

I will let you know if this is the final solution or if i have more question, but all the links and description did not solve the login problem and i did not read anywhere from the password reset solution yet.

SOLUTION CONFIRMED. DOMAIN PASSWORT RESET AND LOGIN POSSIBLE

[Niranjan]

Hi @Philipp Schmidt ,

A feature request was closed as "Invalid" - https://jira.atlassian.com/browse/JRASERVER-2998

I would recommend to deactivate them instead of deleting users. Users cannot be deactivated if they are component or project leads. 

https://confluence.atlassian.com/adminjiraserver/create-edit-or-remove-a-user-938847025.html

You can also remove them groups that has application access in JIRA which would also serve the same purpose. You can remove them from application access groups using script runner. 

https://library.adaptavist.com/entity/remove-specified-users-from-a-group

While you can delete users from database, I would NOT recommend DB updates as they are riskier. 

[Philipp Schmidt]

thanks for the fast replay

i think actually need to delete the user, so the AD user takes over. WIth simple deactivating the AD user can not login or takes not over the Issues from the deleted user.

To clarify, we switched directorys from Jiralokal to AD. The way we moved forward was to delete the Jiralokal user, then the AD user could take over. We had the issue with similar usernames in jiralokal and AD.

We made one misstake by one user and renamed him instead of deleting. Now we can not rename him again because a similar user is already there, we can not delete him because he has many issues open and assigned. We thought the easiest way is to bulk move the issues to the new AD user and remove the old one. Its the same user just in a different directory.

[Niranjan]

@Philipp Schmidt I would recommend you to check this link 

https://confluence.atlassian.com/adminjiraserver/migrating-users-between-user-directories-938847059.html and decide if migrating users by changing the directory order would help.

[Philipp Schmidt]

Hi thank you again for quick response.

I do not have the option for user migration.

It Says

1. This option will not appear if there are no valid directories to migrate from/to.

but i am not aware why i should not be able to migrate my user. I have . I assume i have valid directories.

any idea or help would be appreciated.

[Niranjan]

@Philipp Schmidt - This could be due to the type of your user directory. I believe that you would have configured the LDAP directory in this non-delegated method, which in turn would make it invalid to migrate users to or from.

You may need to configure the LDAP directory again, but this time with a different option 'Internal with LDAP Authentication'

https://confluence.atlassian.com/adminjiraserver/connecting-to-an-internal-directory-with-ldap-authentication-938847055.html

[Philipp Schmidt]

okay, i did as you said and changed the AD to internal with AD authentification.

then i migrated the user localy to localy with AD integration.

when the user tries to logon with AD credentials error: Sorry, an error occurred trying to log you in - please try again.

when he tries to login with local credentials: wrong username or password.

Login is only possible with my local admin which i had to delete and recreate.

All other users or admins are not be able to login.

Error stays regardless which directory i sett as prio 1.

so how do i get out of this mess now?

I can not reset the user passwort somehow.

The user can not set there passwort, they dont recieve emails, but this might be an missconfiguration on our site.

[Niranjan]

@Philipp Schmidt - I am unsure what steps you have performed. DO NOT delete any directory. Just create a new directory, run a full sync and then place it at the top.

The article is for connecting your Jira application to an LDAP directory for delegated authentication. This means that Jira will have an internal directory that uses LDAP for authentication only.  (This may not be your usecase)

If you have internal usernames are available in LDAP, say Bob is under internal directory (Bob is also in LDAP), then use https://confluence.atlassian.com/adminjiraserver/connecting-to-an-ldap-directory-938847052.html - You can connect your Jira application to an LDAP directory for authentication, user and group management.

[Philipp Schmidt]

Hi,

i migrated my users from the local directory to the LDAP directory as you descriped yesteray. Now the users are only in my LDAP directory and not localy anymore.

I tried several things and a lot of settings, but nothing helped. I got error 500, error username and password wrong and so on.

Now i resettet my ad password and it looks like this might be the solution. Now i have to reset from all users the AD password. this shouldnt be the right solution but it works for us now.

I will let you know if this is the final solution or if i have more question, but all the links and description did not solve the login problem and i did not read anywhere from the password reset solution yet.