Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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

4 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.

Suggest an answer

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

JSM Jira Automation: How to Send SLA Breached Notifications

Hi Everyone, In   this tutorial,  we will show you how you can monitor an SLA, and send notifications before or after the SLA has been breached.   SLA Threshold Trigger The SLA t...

662 views 5 12
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