User Export Question

[srinivasp]

We are looking for adding users to target instance from source who are not existing in the target. Idea is not to disturb the existing configuration in target server. Does any options in export, supports this requirement?

[José Marañón [Awnaba Software S.L.]]

In export you would select the option for "Full export" of users. This is the default, so that doing nothing you would be ok.

However, much depends on what you mean by "not to disturb the existing configuration". If you mean, "do not modify existing users in target" then I am afraid that is not supported now. User attributes that could change would be "full name", email address and properties. No existing user would be deleted in any case.

There is an option to ignore users during the import (i.e. no new users would be created, and existing users would not be changed), but that would disable creation of new users in the target.

[srinivasp]

If we disable the option to create new users, what happens to filters and dashboards in the below scenarios?

1. user (who is not existing in target) is owner of filter from source
2. user (who is not existing in target) is part of jql from source

[José Marañón [Awnaba Software S.L.]]

In scenario 1, the filter would not be created, as its owner does not exist. If you enable the option to "continue the import on dashboard and filter errors" the import will go on with the rest of filters/dashboards. Otherwise, the import would stop on that error. Take into account  that there is currently a feature request to create the filter in these cases, assigning it to the user who is running the import. This feature request should be released in two months, more or less. All of this applies also to dashboards.

In scenario 2, the filter will be created and the import will run successfully. If, later on, the filter is executed in the target instance and the user in the JQL does not exist yet, JIRA will show an error to the user running the filter.