New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-10591
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Keith Brophy
Votes: 1
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

CSV Import: Provide a new name mapper to allow re-use of existing JIRA users

Created: 11/Jul/06 09:24 PM   Updated: 26/May/08 06:14 AM
Component/s: Import / Export
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Anton Mazkovoi [Atlassian], Darryl Lee and Keith Brophy
Since last comment: 29 weeks, 6 days ago
Support reference count: 3
Labels:


 Description  « Hide
Allow the CSV importer to re-use a user based soley on the fullname.

For example, if an Assignee in the import (e.g. John Doe) matches a Full Name in Jira (e.g. John Doe), Jira should choose that pre-existing user for the Assignee.

At present, the CSV import will expect the username to be a lowercase concatenation of the fullname or a lowercase first initial concatentation with lastname based on the mapper that is used.

For example, if a user with username jdoe and fullname John Doe exists within JIRA - the CSV import will create a new user with username johndoe and fullname John Doe. In this case, the pre-existing user should have been used.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Darryl Lee added a comment - 30/Jan/08 06:32 PM
This bug has the wrong component, it should be Import/Export, as it is related to CSV (comma-separated values), not CVS (version control).

Anton Mazkovoi [Atlassian] added a comment - 31/Jan/08 11:21 PM
Thanks. I have fixed the component.