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

User inactive in Crowd, but it is active in AD.


My company was using shared mailbox for HR, but it turns out, that Crowd mark those accounts as inactive. 

So we made this account as a normal user, not as a shared mailbox, but this didn't help. In crowd I can see, that this user is still not marked as active. I tried the full sync, but it didn't help. What can we do more to make it working? 

We only want to be able to send emails from this mailbox to Jira, to create new tickets. But in logs we can see, that Jira rejected those emails, cause this user is not active.

2 answers

So I corrected my issue by updating the field records in the Crowd database manually. We had to do this because we have read only access to active directory. Our admin accounts done have email addresses so we are unable to update the crowd user account because it requires an email address.

I ran:

UPDATE cwd_user SET active = 'T' WHERE user_name LIKE 'my admin name criteria' AND active = 'F';

Damian did you find an answer for this? We're experiencing the same issue. I have 6 admin accounts created in our AD structure to use specifically for managing our Jira instances. 5 of the 6 accounts show INACTIVE. The users are able to log in with these accounts but the accounts but after a very short period of time are forced logged off.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events