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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,463,709
Community Members
 
Community Events
176
Community Groups

After migration customers cannot access their tickets any more

We migrated from Jira Servie Desk (Server) to Jira Service Management (Cloud).

Alls Issues and Customers were migrated (with the migration app)

If a customer tries to sign on on the new site, he is told something about singel sign on, receives a new registration email, has to choose a new password and is asked questions about his position and so on (like when I registered). This is very confusing to our customers.

And if the customer has done all this - he has no access to his issues. The customer must be removed and added again to restore access. Doing this for all our service projects and customers would be hours of work (and confuse the customers even more).

So:

  1. Why has a customer to register again? Can that be circumvented?
  2. Why is the customer asked questions on registration like if one of our employees is registering ("what is your postion/function")? Can I disable that?
  3. Why after all this, the customer has no access to his issues/service desk? Is there any other solution than removing and readding each customer?

Bonus question: :-)

The old url of our (Server) Service Desk was more readable. It uses the service projects key. The new (Cloud) url is much longer and contains a portal number instead. I can't remember that I intentionally configured this in the old Service Desk. Can that be changed in the cloud somehow to the same style than we had before?

Thanks a lot. I hope this are not all annoying beginner questions. :-)

1 answer

1 accepted

7 votes
Answer accepted

We solved it.

The Service Desk Cloud Migration App has created an Atlassian Account for every customer.

If an E-Mail ist registered as a customer AND an Atlassian Account, the user is forced to register and is now treated as his Atlassian Account, which is different from his customer account and therefore has no access to the issues.

The solution was to manually delete all the hundreds Atlassian Accounts.

Hi @Holger Thiemann 

Thanks for sharing! It has been some time ago now, but if you by any chance see this comment could you share how you have preserved the association between reporter and issue if you have deleted all Atlassian Accounts after migration? Have you re-done migration or any other approach? 

Thanks! :)

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events