I am attempting to split our current JIRA Cloud instance by moving two projects into a new instance. I realize this means exporting all of the issues for all of the projects on the source instance, importing them into the target, and then deleting the ones I do not want.
My questions involve moving the user accounts to the new instance:
Hi Jason,
from Jira-documentation:
If you are importing a username-based CSV field (e.g. Reporter or Assignee) and you do not select the Map field value checkbox for this field in the previous step of the CSV file import wizard, then the importer will automatically map imported usernames from the CSV file to (lowercase) JIRA usernames.
Regardless of whether or not you select the Map field value checkbox, JIRA will automatically create usernames based on the data in your CSV file if they have not already been defined in JIRA.
(https://confluence.atlassian.com/adminjiraserver071/importing-data-from-csv-802592885.html)
Since these users were created without email-address, there should be no email sent to them. But to be sure, you can disable the email-server before importing.
You should also try your import before in an testing environment.
Given our user license is limited we can't afford for JIRA to automatically create all the users associated with the issues, i) we don't have enough spare licenses and ii) the vast majority of these people have left the organisation.
We can't delete the users prior to export as they've commented on thousands of issues.
I've tried removing them from all roles and setting each one to Inactive, but as stated above it creates the Users, but not only that it sets them active again. Note, I'm doing this trialling on a test instance.
What would be your recommended approach to importing a project into our Production instance?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would expect the users to be created, and I don't think that welcome emails would be sent to each user.
You could test this by unzipping the exported XML file, doing a global replace to make them all invalid, manually fix one for yourself to be valid, then import
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.