Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Deleting shadow users with ScriptRunner

tl;dr: I want to delete shadow users in the Jira 'internal' directory that are currently authenticating against an external directory.

Past threads that come close to this request talk about database operations a lot, and they're many years old. I know the two ways to do this are both pretty gross, like:

1) Disable or rename users in the primary directory to expose the old internal users again, and delete them, or

2) Delete from the database, being sure to hit cwd_users and cwd_memberships.

But what about with ScriptRunner? Most of the interfaces are obsessively focused on ApplicationUsers, which isn't helpful (doesn't return shadow users). I can get to a directory-level user via the embedded Crowd interface, but none of those interfaces seem to have user deletion methods.

Is ScriptRunner a dead end or am I missing something? Is a database operation still the only way to do this?


Situation (and why I'm not just "ignore them, they aren't hurting anything") -- we're ditching Crowd and migrating back to Jira internal users. Since we originally migrated from Jira internal to Crowd, many present day users still exist, but with severely outdated info. Rather than reactive and figure those out, it seems simpler to nuke the old internal accounts and copy their up-to-date equivalents over fresh.

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events