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

Need to sideline imported JIRA users

We imported from a JIRA 4.1 server to the Cloud recently, and the process involved stepping through about 4 intermediate upgrades. 

In our JIRA 4.1 server, we had one account set up for each customer and each customer had a separate support project.  All access to the customer support project was via the API using the user account credentials for the customer, and the reporter for the issue was set to the customer user account.  Email addresses of a contact at the customer was set in the customer user support account. 

After importing to the cloud, these customer support user accounts have had all access revoked. 

We now use JSD to handle all customer initiated help tickets and occasionally linking to a JIRA project when time required to resolve exceeds a certain threshold. The problem that I am having is that when I try to add a customer to JSD as a JSD customer and the email address of the individual is assigned to the old JIRA support user account, JSD will not let me. It identifies the email as an existing inactive JIRA user.  

Here is a weird thing:  In the JIRA user screen, I can "delete" the old support account, but it doesn't really delete it, even though the process completes with an affirmative message. Yet after going through the "delete" process, I can then add the customer email on as aJSD customer without complaint.

That is not (unsurprisingly) solving anything.  When the customer tries to log into the JSD portal, he is taken to the general Atlassian login for active users, and is allowed into the old JIRA project (even though he has no site access).  

It seems that if I could just change the email addresses (to a 'dummy' email address) on the old user support accounts the problem would go away. The only way Jira Cloud lets me do that is by emailing the email change request to the customer for approval. I just went through the process with a customer and she got the email change request, but it didn't change the email in the old account, it create a new user in Jira with the new address. Even if it did work, I would rather not have to go through that process 40 times.

So, how much of a mess have I made and what is the best path forward?


Ismael Jimoh Community Leader Jan 18, 2020

Hi @Tom McCobb 

In this case, do the following:

  1. Activate the user
  2. Remove the user(s) from all groups that grant access to an application (all license consuming group)
  3. After this these users can be added as customers.



Log in or Sign up to comment