Hi Philippe,

I actually ran the test myself and found that data associated with the deleted user will continue to be associated with the username. The username will not be listed in the userbrowser and there is no link to their profile, they are simply a placeholder with the username.

Regards,

David Chan

Hi folks,

Just an update: JIRA 4.3 will resolve this issue. It's due Q1 2011.

Cheers,
Dave.
Product Manager.

We're currently reworking JIRA's entire user management stack to use the guts of Crowd (see JRA-1962) for more.

That work will make this issue obsolete. Not today, but soon...

Cheers,
Dave.

Perhaps if the user isn't found, Jira could fallback to using the Project Lead? It could display a small indicator to show that an action wasn't made by the actual Project Lead but by Jira itself as there was a user error when the action was performed.

Won't Fix, Seriously? This is a key feature of Crowd, central user control.

Here is the proposed fix: When a user is 'deleted' from crowd run an update against jira & reassign the tickets from the user to 'Unknown', or make a free user named 'Deleted' and assign them to him Done...

I did find another work around for this issue too...!
Inside Crowd > Applications > Jira > Permissions > Uncheck 'Remove User' (see below)

"Remove User"
"Allow users to be removed from the directory."

If you remove this permission from crowd, it can't delete the users.

This bug is a MUST FIX if you really want to market Crowd as an "SSO".

Completely agree with the abovec comments. This is not a usable work around.

Won't Fix? I agree with Darren, we have too many users to manage, and we have a corporate policy that states we must disable old user accounts upon employee termination. How am i going to regain control of the thousands of tickets that belong to ex-employees?

This issue may keep us from adopting Crowd in our corp environment.

What if you are managing 10,000 users and the corporate I/T policy is to disable the accounts to all applications including crowd cannot see them?

I think it is premature to close this issue if Atlassian wants to attract larger install bases.

This really is a Jira problem, and unfortunately the associated Jira issue is a low priority citing this workaround.

Workaround

One of the unfortunate aspects of this bug is that JIRA will not let you re-assign any issues for which the deleted user is the assignee, because it instead throws the DataAccessException.

The fix is to re-create the user in Crowd. Then you can re-assign the issue, as the exception will not be thrown.

You can then deactivate the unwanted user (better to deactivate than delete).

Please feel free to vote for the relevant JIRA issue.

This issue is caused by JIRA's inability to handle the deletion of a user that has issues assigned to them, and is not a Crowd-specific issue. To be honest, there's not a lot Crowd can do to fix the problem. There are, however, some workarounds available:

Users of Crowd with Internal Directories:

• Disable the user rather than deleting them.

Crowd with LDAP or custom Directories:

• Turn External User Management Off in JIRA.
• Use JIRA's UI when you wish to delete a user.
• JIRA will not allow you to delete users that have issues assigned to them.

JIRA will, at some stage in the future, be reworking their user management, which will resolve this issue.

This is still blocking us. See
Any updates?