Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

What is the correct way to setup Crowd with existing instances of Confluence and Jira

First we had Confluence and setup users in it. Then we added Jira and setup users in it. Now we have Crowd. How do we get the users from Confluence and Jira into Crowd so all the existing assigned issues, tasks, pages in Confluence etc. are the same? Backwards, I know, but that's where we are.

1 answer

1 accepted

0 votes
Answer accepted
Marcin Kempa Atlassian Team Feb 02, 2018

Hi @Gary Spencer,

There are couple of questions in need to ask before I can suggest a solution. Do you have the same set of users between Jira and Confluence? Do you have the same username scheme between applications? (for example both Jira and Confluence have users with names like 'jdoe' rather than Jira have 'jdoe' and Confluence 'john.doe')

Do you want all of the users to be now in Crowd or only some subset? Were those users created manually or users accounts were created by users themselves using public signup?

If both applications contain same set of users, you can try using import feature as described here and import users from one of your applications. Then as user matching is based on username itself, once you switch to Crowd directory in Jira and Confluence your users should still have access to it and history should be maintained.

I suggest testing how it works for you on some staging environment before rolling this up to production. 

Instead of removing internal directories in both applications I suggest disabling them. for now. In general it is better to administer users in one place and not duplicate them across applications. The only exception is to leave a unique sysadmin in internal directory in Jira and Confluence so you still can have access to those applications even if Crowd application cannot be reached.


Hope that helps,

Marcin Kempa

Hi Marcin,

The usernames were the same in some cases but not in others. Because we are small I ended up creating new accounts in Crowd, renaming old accounts in the other apps and recreating the permissions. 


Marcin Kempa Atlassian Team Feb 02, 2018

Thank you for reply,

I am glad that you were able to solve this problem. 


Best Regards,

Marcin Kempa

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

181 views 6 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you