I am importing issues from JIRA 3 to JIRA 6. Works like a charm. I have optimized the setup for it, except for 1 thing:
- E-mail Suffix for new users has not been filled in - our users have different e-mailaddresses.
- In the Fields-screen, I did map the assisgnees and reporters.
When the import is done, I have double users. e.g. "v.valkestijn@mycompany.nl" (which I have set up earlier through LDAP) and "v.valkestijn@" (are now Internal JIRA users). The system doesn't recognize that these are the same users.
How do I solve this?
Found it! Map the Reporter and the Assignee. Overlooked / didn't understand that in the first place. When you still choose to fill in nothing, it becomes a "user@" or else it's assigned/reported to the user you define. Awesome!
Hi Vera,
CSV Importer is matching users via username or Full name or e-mail address. So to make the importer find the appropriate user you need to provide one of this free values. So for example, if you have a user:
Username: Bob Fullname: The awesome Builder email: bobthebuilder@example.com
You can prepare CSV file which would look like this:
Summary,Assignee Bug1 ,Bob Bug2 ,The awesome Builder Bug3 ,bobthebuilder@example.com
This would create three bugs and in each one of them will have Bob as assignee. If you would put only "bobthebuilder" in Assignee column, it would result in creating new user, as importer cannot match it with any of the user fields (we are not cutting the email suffix while matching).
I hope this helps,
Cheers
Przemek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'll try that too later, thanks!
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.