-
Bug
-
Resolution: Won't Fix
-
Highest
-
None
-
None
-
None
When a user is removed through Crowd, if the user has linked in data with JIRA a DataAccessException is thrown resulting in an error screen in JIRA.
- is caused by
-
JRACLOUD-2073 Deactivating user - assigning all issues to other user
- Closed
-
- Closed
[CWD-202] JIRA throws DataAccessException when an external user (Crowd) is removed.
Philippe Muller
added a comment - David : How does JIRA 4.3 fixes that issue ? 
David O'Flynn [Atlassian]
added a comment - Hi folks,
Just an update: JIRA 4.3 will resolve this issue. It's due Q1 2011.
Cheers,
Dave.
Product Manager.
David O'Flynn [Atlassian]
added a comment - Hi folks,
Just an update: JIRA 4.3 will resolve this issue. It's due Q1 2011.
Cheers,
Dave.
Product Manager. David O'Flynn [Atlassian]
added a comment - 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.
David O'Flynn [Atlassian]
added a comment - 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. 
Scott Wallace
added a comment - 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.
Scott Wallace
added a comment - 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. 
Anthony Vierra
added a comment - 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".
Anthony Vierra
added a comment - 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". 
Jesper Hoejgaard
added a comment - Completely agree with the abovec comments. This is not a usable work around.
Jesper Hoejgaard
added a comment - Completely agree with the abovec comments. This is not a usable work around. 
Rob Terhaar
added a comment - 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?
Rob Terhaar
added a comment - 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? 
Darren Martz
added a comment - 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.
Darren Martz
added a comment - 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.
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